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: ISO9000: what you make is what you claim to make
Subject:Re: ISO9000: what you make is what you claim to make From:"Walker, Arlen P" <Arlen -dot- P -dot- Walker -at- JCI -dot- COM> Date:Mon, 1 Dec 1997 10:24:09 -0600
Now, please, tell me if and when ISO9000 force you to tell your
customer WHAT you want to produce.
I would think the customer forces that. If I don't tell you what I'm
making, how can I realistically expect you to buy it? And if my competitors
don't tell you, but I do, doesn't that give me an advantage over them in
selling to you? ISO9000 doesn't have to force anything, the market system
does that all by itself.
Are you, manufacturer, forced to give me a data sheet that describe
your product and tell me the quality level you decided to keep? Have
I (individual customer) access to your product's project and ISO9000
If you don't get that access, perhaps you, as a customer, should ask why
you don't. Seems dangerous to me to buy something without knowing what it
is you're buying or who you're buying it from.
How can I tell you if your product's features comply with my wish
Compare your wish list with my spec sheet. Or do you seriously mean to
suggest anyone should buy something without checking the specs on it first?
How can I tell you if I'm willing to accept your cost/compromise
By opening your checkbook or not. If you don't buy, obviously there's
something about it you didn't think was worth buying. I can either ignore
the fact you didn't buy, or ask you why. You can either tell me or not. If
I don't ask, I can't improve. If you don't tell me, you make it difficult
for me to improve.
Why should not I be legitimate to read it as a general claim of
"high" quality? Why should I think that my idea of "high quality" was
incorrect? Did you warn me of my "phylosophical" mistakes?
Since I wouldn't be aware of your "philosophical mistakes" unless you told
me about them, I could hardly warn you about them in advance, now, could I?
If I put any statement at all about the quality of my product on my box,
how would you know the truth behind it? You'd have to examine my claim to
see what it means and to see if it was true. You should treat ISO9000
certification the same way. It's rather senseless to give the certification
a high value without knowing what it means, isn't it?
Are not you, ISO9000 certified company, hiding yourself in a
bureaucratic maze? Do you really think customers will not realize it?
My company went for certification for several reasons, and one of them was
because our customers demanded it. They obviously didn't think we were
using it to hide in a maze. ISO9000 isn't hiding anything. The meaning of
ISO9000 is clearly defined and easily available. If a customer doesn't want
to bother to check what the ISO9000 certification means before using it to
make a purchasing decision, then I'd suggest that the quality of their
purchases is probably not their only problem, nor even their most pressing
It seems to me your objections aren't really about ISO9000 at all. They
seem to be more about sleazy business ethics than about quality management
Chief Managing Director In Charge, Department of Redundancy Department
Arlen -dot- P -dot- Walker -at- JCI -dot- Com
In God we trust; all others must provide data.
Opinions expressed are mine and mine alone.
If JCI had an opinion on this, they'd hire someone else to deliver it.