J
JaneB
Re: QMS (Quality Management System) Manual - The Boss Wants a 4 Page Manual - What to
It's a quality management system we're after. And the system consists of more than just documentaitn. It's not a 'document everything' or a system of documentation. Yes, doco is required. Yes, there's a need to write stuff down. But what, how and how much is an individual decision.
I prefer an approach that recognises it's a management system to the one that wants to write down (re-interpreted or otherwise) every single requirement.
Ultimately it needs to work for the individual organisation in their context, with their customers, their unique needs and their products/services and resources. There isn't (and shouldn't) be any 'one size fits all'.
Me neither!People don't need to know what a 'standard' requires them to do in their daily jobs. They need to know what their prganisation expects them to do - full stop, period, point!
... The skill of the quality professional (as I have said 431 times before) is to take ISO standards, read through ISO speak and assess: 'What does this mean for my organisation?' and then go about explaining to the folks in his / her organisation what changes need to be made - if any.
If we go about documenting an 'ISO' system rather than the organisation's real management system then we are doomed to be 'the document guys and gals' and all we are there to do is defend the documented system against the invading (barbarian) hordes of auditors - not a job I want.
No, it doesn't. After all, if the organisation has formally committed to a QMS that meets ISO 9001, that covers it. What on earth then is the point of then repeating all the detail of the standard with 'Joe Bloggs Ltd's policy is' in front of it?There are plenty of things that need documenting but, for example (at random): 'It is Joe Bloggs Ltd.'s policy to ensure that we maintain the infrastructure necessary to ensure product is manufactured in accordance with ... blah, blah, blah ... is not one of them and therefore has no place in a manual.
It's a quality management system we're after. And the system consists of more than just documentaitn. It's not a 'document everything' or a system of documentation. Yes, doco is required. Yes, there's a need to write stuff down. But what, how and how much is an individual decision.
I prefer an approach that recognises it's a management system to the one that wants to write down (re-interpreted or otherwise) every single requirement.
Ultimately it needs to work for the individual organisation in their context, with their customers, their unique needs and their products/services and resources. There isn't (and shouldn't) be any 'one size fits all'.