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.
Subject:Re: ISO 9000 From:Smokey Lynne L Bare <slbare -at- JUNO -dot- COM> Date:Tue, 16 Jun 1998 00:48:35 -0400
Dear Hani,
First, ISO processes are referred to as either paying to be externally
audited and becoming Registered, or internally audited to become
compliant, unless in the British Isles, where it is 'certificated'.
Second, your question is way too broad in spectrum. It is like asking
what breed of horse do you like, or what athletic pro sport is the best
for pro-rule sanctions. You need to be specific. Compliancy works well
for some instances, and other, more serious-outcome instances should have
their processes Registered.
Service organizations (computer and project management firms) are seeing
the importance of becoming Registered, as it is usually their only taste
of an internal QA process. It also is a wonderful 'business-getting'
marketing tool. You should check the archives, as Mr. Robinson set up a
wonderful explanation, and provided a definitive structure on how to
judge if you are a candidate for ISO methodology or not.
