TechWhirl Sponsors

About TechWhirl

TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.

For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.

Re: question re: TW to Quality Management

You don't actually have to be a QA professional to implement a QMS. I've
seen it done by small startups that didn't have a QA dept yet.

The important things are to document everything you want an ISO auditor
to verify and don't document anything you don't want an auditor to
check. There is no requirement in ISO to document everything you do,
but when the auditor shows up, you'd better be doing everything you
documented the way you documented it.

Remember that creating your QMS is like tying the noose you may be hung
with. Don't make it so tight that you can't slip out of it if you have to.

Gene Kim-Eng

On 11/19/2012 1:14 AM, Alison Wyld wrote:

Many thanks to all who took the trouble to reply to my ill-spelled question
on this subject. There is a lot of expereince out there !

The actual role we are talking about is the job of putting in place a
Quality Management System (maybe ISO9K...) for a smallish software company.
Based on my reading and on various input from readers of this list, I think
it could work out.