posted 23 March 1999 10:08 AM
I asked what I should say to convince prospective clients that their system should be documented and comply with ISO 9000. I certainly got some good feedback. To summarise, Iāll pick out the points that I felt stood out and which I will use in my contact planning. Thanks to all who contributed;Kevinās contribution;
is critical but I would change it to ĪItās not just paper. You need it to focus on the system.ā (JC; adding in Īnotā and Īitā.) Understanding and training.
ĪIt ensures nothingā - (JC;Yes my clients need to know that.)
Don;
Management commitment and commitment to long term goals, simple, direct. The person responsible having the freedom to do what is right. Systems usually fail due to lack of this commitment and freedom.
Christian;
ĪDocumentation is most important when things go wrongā
ĪDocuments are a contractā.
(JC; A very strong point indeed and one that I havenāt come across before. When I was given supervisor training many decades ago, I was told, ĪNever end a discussion with a worker without double checking they understand what you want and intend to do itā.)
Bryon;
Donāt put the standard before the customer.
(JC; In my experience, this is the most powerful point of all. People who concern themselves with compliance, get in the way of those who concern themselves with productivity. ((Iāve said that before)) You ask for comment; I would say, that Īproductivityā is king, not the customer. Give marketing and the finance guys the tools they need ((ie the right product at the right cost)) to grow the company and make the customer happy. Internally, keep your eye on the ball, which is making sure it is the right product and reducing costs to make your cost of sale more satisfactory to both company and customer. So I wouldnāt argue with the Īcustomerā focus, but it isnāt everything.)
Marc.
Contract between supplier and customer.
(JCOf course. But that is the original and basic reason for ISO 9000; To demonstrate ((by third party inspection)) the supplierās capability. Section 1 Scope.)
The idea of making management liable
(JC; is a very good one, but not one that will help me convince my client to give me business.)
(JC; Interestingly, ĪLiabilityā is what ISO 9000 is not about. It is about avoiding liability. If we become the target of liturgation because our product ran amok in the main street of Montevideo, we gather up all our quality evidence and carry it in a wheelbarrow into court, making the case that we are innocent and the incident was an act of God.)
Byron again;
Itās all down to money.
(JC; Powerfull point. We sure wouldnāt make the customer happy if we werenāt going to come out well from it. Nor will we continue to make him happy if we go out of business.
Most important - My client knows this. If ISO 9000 doesnāt improve productivity or open doors to sales, then my client wonāt want it. And right too.)
Christian;
The harm those words can do. ie; Quality, ISO 9000.
(JC; Right on. So many times I walked into a supplierās reception;
ĪHello, Iām John C, Supplier Quality Engineer, Apple Computerā
ĪOh hello, please take a seat and Iāll get xxx our quality inpector or yyy our quality manager, etc, etc.ā
ĪI donāt want your quality anythingā, I would say, ĪI want the manufacturing manager who made the damn things wrong in the first place.ā)
Thanks again. Itās powerful stuff.
and rgds, John C
[This message has been edited by John C (edited 03-23-99).]
[This message has been edited by John C (edited 03-23-99).]
[This message has been edited by John C (edited 03-23-99).]