ISO 9001 is the most widely used quality standard in the world, and one of the most widely wasted. The common pattern is depressingly familiar: a business wants the certificate because a customer or a tender demands it, so it writes a pile of procedures nobody reads, passes the audit, frames the certificate, and carries on exactly as before. It now has all the cost of ISO 9001 and none of the benefit. The standard did not fail. It was used as a hoop to jump through rather than a discipline to adopt, which is a choice, and a bad one.
What ISO 9001 is actually asking for
Underneath the clauses, ISO 9001 asks a few genuinely useful questions and expects you to answer them honestly. Do you know your processes, how the work actually flows from a customer's request to a delivered result. Do you know what could go wrong in each, and have you done something about it. Do you measure whether the work is any good, and act when it is not. And do you improve, using what goes wrong to get better rather than just recording it. Those are not bureaucratic questions. They are the questions any well-run business should be able to answer, and the standard just insists you write the answers down and live by them.
The heart of it: the process approach
The most valuable idea in ISO 9001 is the process approach, which sounds dry and is not. It means seeing your business as a set of connected processes with inputs, outputs and owners, rather than as departments that throw work over walls at each other. Most quality problems live in the hand-offs between departments, the gaps where sales assumes operations knew and operations assumed sales checked. The process approach makes you look at the whole flow and own the hand-offs, which is exactly where the defects hide. That single shift, from departments to processes, is worth the price of the standard on its own.
The solution, as a process-approach checklist
Make ISO 9001 improve the work
- Map your core process end to end, from the customer's request to the delivered result, across every department it crosses.
- Name an owner for the whole flow, not just for each department's slice.
- Find the hand-offs, the points where work passes between people, because that is where defects hide.
- Decide what "good" looks like at the end, and measure whether you hit it.
- When something goes wrong, trace it to the process and fix the process, not just the person.
- Write down only what a new person would actually need to do the job right. If nobody would read it, it is not a control.
The test of a good quality system
Here is a simple test. If you took your ISO 9001 documentation away tomorrow, would anything about how the work is done actually change? If the honest answer is no, your quality system is decoration, and you are paying for a certificate that changed nothing. If the answer is yes, if people genuinely rely on those processes to do the work well, then you have the real thing, and the certificate is simply proof of a discipline you would want anyway. Aim for the second. The audit is easy to pass when the system is real, and painful to fake when it is not.
Questions to test your quality system
- If we removed the ISO documentation, would how we work actually change?
- Do we manage our business as connected processes, or as departments over walls?
- Who owns each core process end to end, across departments?
- Where are the hand-offs, and do we watch them for defects?
- Did we write procedures for the auditor, or for the person doing the job?
ISO 9001 is a good standard held badly by most of the businesses that hold it. Used as a hoop, it is expensive paperwork with a certificate at the end. Used as intended, it is a discipline that maps your real processes, owns the hand-offs where defects hide, measures whether the work is good, and improves it, with the certificate arriving as a by-product of running well. Choose the second version. It costs the same in effort and returns something worth having, instead of a nicely framed receipt.
Notes and sources
From the book
Key Quality ModelsFifty models and standards of quality assurance, each explained in plain language and told through a real, sourced case.