tmoreau
2nd February 2009, 01:30 PM
I know this might seem like a dead horse to many, but I'm not satisfied that it is.
Is this a workable quality policy?
Continually Meeting Expectations
We will meet customer requirements in design and manufacturing, establish methods to measure the performance of our company, and encourage continual improvement in all aspects of business through compliance with ISO 9001.
Requirements per Iso9001:2008 section 5.3
Requirement A: Be appropriate to organization's purpose
Covered: Yes ("meet customer requirements in design and manufacturing")
Requirement B1: comply with requirements [of ISO standard]
Covered: Yes ("through compliance with ISO 9001")
Requirement B2: Use the words "continual improvement" (or for purists, demonstrate commitment to continually improve effectiveness)
Covered: Yes ("encourage continual improvement in all aspects of business")
Requirement C: Provide a framework for establishing & reviewing quality objectives
Covered: Yes ("establish methods to measure the performance of our company")
Requirement D: communicated & understood within the organization
Covered: Covered elsewhere, not as part of quality policy (see mgmt. review)
Requirement E: review for continuing suitability.
Covered: Covered elsewhere, not as part of quality policy (see mgmt. review)
Our quality policy was established simply as "Continually Meeting Expectations" some ten years ago. Without further explanation or argument, that seems to fail the requirements above (evidenced by reaction of auditors), so it is being expanded to serve an auditor (which is why it exists in the first place), not for any benefit to the company.
We all seem to ASSUME the typical interpretation that a "quality policy" is a laminated pocket sized lofty quote that everyone should memorize. Why? What is "policy"? Lets rephrase, you are asked "what is your countries foreign policy, and what does it mean to you?" How would you answer? Would you pull out a laminated pocket-copy and quote it in its entirety? I cannot determine how this quarter-page version of "policy" is supposed to help anyone or any organization.
You can see I am leaning toward a different interpretation entirely, what if:
This document and our procedures form the [COMPANY] Business Manual, otherwise known as a Quality Manual, Quality Policy, or Quality Management System.
The quality manual ("this document") is three pages, mostly diagrams rather than text. The procedures raise the total to 21 pages. Altogether, that's our policy. We could drop the "Continually Meeting Expectations" catch-phrase and the forget the expanded version. I cannot find a requirement in the standard that the quality policy be a statement, or that a quality statement exist.
But then, I'm a little too humble to think this is a proper interpretation and I'm the only person to discover it. On the other hand, I don't want to just go with the flow (adopt policy quoted above) if there is no measurable benefit.
Ultimately, the requirements of the standard will be addressed more verbosely in greater detail throughout our system (our policy). A 'statement' is wholly redundant, by the time all the requirements are reduced to a single statement it is meaningless jargon. I want to skip that, its anti-lean. Can I get away with it?
Is this a workable quality policy?
Continually Meeting Expectations
We will meet customer requirements in design and manufacturing, establish methods to measure the performance of our company, and encourage continual improvement in all aspects of business through compliance with ISO 9001.
Requirements per Iso9001:2008 section 5.3
Requirement A: Be appropriate to organization's purpose
Covered: Yes ("meet customer requirements in design and manufacturing")
Requirement B1: comply with requirements [of ISO standard]
Covered: Yes ("through compliance with ISO 9001")
Requirement B2: Use the words "continual improvement" (or for purists, demonstrate commitment to continually improve effectiveness)
Covered: Yes ("encourage continual improvement in all aspects of business")
Requirement C: Provide a framework for establishing & reviewing quality objectives
Covered: Yes ("establish methods to measure the performance of our company")
Requirement D: communicated & understood within the organization
Covered: Covered elsewhere, not as part of quality policy (see mgmt. review)
Requirement E: review for continuing suitability.
Covered: Covered elsewhere, not as part of quality policy (see mgmt. review)
Our quality policy was established simply as "Continually Meeting Expectations" some ten years ago. Without further explanation or argument, that seems to fail the requirements above (evidenced by reaction of auditors), so it is being expanded to serve an auditor (which is why it exists in the first place), not for any benefit to the company.
We all seem to ASSUME the typical interpretation that a "quality policy" is a laminated pocket sized lofty quote that everyone should memorize. Why? What is "policy"? Lets rephrase, you are asked "what is your countries foreign policy, and what does it mean to you?" How would you answer? Would you pull out a laminated pocket-copy and quote it in its entirety? I cannot determine how this quarter-page version of "policy" is supposed to help anyone or any organization.
You can see I am leaning toward a different interpretation entirely, what if:
This document and our procedures form the [COMPANY] Business Manual, otherwise known as a Quality Manual, Quality Policy, or Quality Management System.
The quality manual ("this document") is three pages, mostly diagrams rather than text. The procedures raise the total to 21 pages. Altogether, that's our policy. We could drop the "Continually Meeting Expectations" catch-phrase and the forget the expanded version. I cannot find a requirement in the standard that the quality policy be a statement, or that a quality statement exist.
But then, I'm a little too humble to think this is a proper interpretation and I'm the only person to discover it. On the other hand, I don't want to just go with the flow (adopt policy quoted above) if there is no measurable benefit.
Ultimately, the requirements of the standard will be addressed more verbosely in greater detail throughout our system (our policy). A 'statement' is wholly redundant, by the time all the requirements are reduced to a single statement it is meaningless jargon. I want to skip that, its anti-lean. Can I get away with it?





