Ask a quality manager who was there in the 1990s what quality management meant back then, and the answer often comes with a warm smile: ring binders. Shelves of them. Procedures for everything, records of everything — and an annual audit where the paperwork had to be in order. Those systems built a discipline and a traceability many companies had never had before, and they deserve respect. But they also left behind a habit that is now the biggest untapped opportunity in many quality systems: we still record more than we act on. The good news? The distance from record to action is shorter than most people think — and the gain is already sitting in your data.
The system did what it was designed to do
When ISO 9001 was published in 1987, the task was to create trust between customer and supplier, and the instrument was documentation: say what you do, do what you say, and prove it. Twenty elements, a quality manual and records that could be produced on demand. That was not a mistake — it was the best answer of its time, and it professionalised an entire generation of companies.
But a system always shapes the behaviour of the people working in it. And a system that rewards producing records gets exactly that: beautiful logs. The action behind the record had no field in the form — so it became optional. That is worth understanding, because it is the same mechanism governing your system today: what the system makes easy and rewards gets done. If you want more action, don’t appeal to people — build the action into the system.
The standard led the way
The powerful part of the story is that the quality world learned its own lesson. When the criticism arrived in the 90s — most sharply from John Seddon, who in 1997 described how the certificate could end up as “recognition of an effective bureaucracy” — the standard responded with its biggest renewal ever. ISO 9001:2000 put the process and its effect at the centre and cut the documentation requirements drastically. The 2015 revision built further: risk thinking instead of ritual procedures, and responsibility placed directly with top management. The coming 2026 revision continues in the same direction: less ritual, more real control.
The message from 25 years of standards development is liberatingly simple: you may record less. In return, what you do record must lead to something. That is not a tightened requirement — it is an invitation to tidy up.
"A measurement no one acts on is not quality management — it is storage. Give it an owner and a reaction, and it starts working for you."
— Prozanta Operations
Example 1 — The deviation log
A typical picture from production: the same label printer keeps acting up, and the operator dutifully writes it in the log — twelve times in a quarter, each entry closed with “adjusted”. The log is in order; the printer is not. The fix is small: the third time the same deviation appears, it automatically triggers a root cause analysis with an owner and a deadline. Five whys later, it often turns out to be one worn component or one missing standard — and then the deviation is gone, not just filed. Twelve records became one action. That is the whole difference.
Example 2 — The complaints folder
The monthly report says “7 complaints”, the number gets a nod, and the meeting moves on. But the number hides a pattern: lay the complaints from the past six months out on a table — quite literally — and sort them by cause. In many companies that exercise shows that most of them spring from one or two process steps. Suddenly “7 complaints” is not a figure to note, but an arrow pointing at the next improvement. The records were there all along; they just needed to be asked a question. How to build that routine in, we cover in Quality systems that work.
Example 3 — The sheet on the wall
The temperature log that has been filled in faithfully every morning for years. Ask what should happen when the number is outside the limit — and the room often goes quiet. The fix: give the measurement a reaction limit and an agreed action (“above 6 degrees → stop, check, call”). If no reaction can be formulated, that is an honest signal the measurement can be retired. Both outcomes are a win: either the measurement now works — or time has been freed up.
Four steps from archive to engine
- •Map first: Go through your records with one question — “when did this last lead to an action?” That gives an honest picture without changing anything yet.
- •Build the reaction in: Every measurement and log that passes the muster gets an owner, a reaction limit and an agreed action. The rest is retired with a clear conscience.
- •Execute in the everyday: Move quality data from the monthly report to the daily board meeting, where deviations can get an owner the same day. There — not at the audit — is where quality is decided.
- •Anchor it: Follow up on whether actions close on time and whether the same deviations fall over time. That is the real test — and it only holds if the follow-up itself has become a routine, not a campaign.
One precondition: make it safe to record honestly
The road from record to action runs through trust. W. Edwards Deming reminded us that a system where records are used to assign blame gets fewer and prettier records — and more hidden problems. So treat every deviation as information about the process, never as an accusation against the person — because the problem is rarely the employees. The leader who says thank you for an uncomfortable record has just bought honest data for a long time to come. That is the behaviour everything above rests on — and the culture follows when leadership leads through action.
✓The most important takeaways
- →The systems of the 90s built the discipline — your job today is to build the action on top. The foundation is already paid for.
- →Record less, act on everything: every measurement must be able to answer “who does what when it shows red?”
- →Recurring deviations are not noise — they are your best-documented improvement opportunities. The patterns are already in your logs.
- →Start with the mapping: one honest question — “when did this record last lead to an action?” — shows exactly where to begin.
Going through your records and finding the ones that never lead to action is, in practice, a mapping of where your quality system has untapped power — and that is precisely the kind of work we start with when we help companies move from records to rhythm: map, build, execute, anchor — and stay in operations until it runs by itself. For a quick pointer first, the operations check takes a few minutes.
Sources
- Seddon, J. (1997). In Pursuit of Quality: The Case Against ISO 9000. Oak Tree Press.
- BSI Group — The history and future of ISO 9001 (whitepaper).
- Deming, W. E. (1986). Out of the Crisis. MIT Press.
- Juran, J. M. & De Feo, J. A. (2010). Juran’s Quality Handbook (6th ed.). McGraw-Hill.
- American Society for Quality — ISO 9001:2015 (ASQ knowledge resource).
The references show the professional basis. Sources are reproduced in their original language.