QualityBy Henrik5 min11 July 2026

From ring binders to rhythm: how quality work became simpler, and why few use it

Quality management in the 1990s recorded everything. Today the requirement is that what is recorded leads to an action.

QualityISO 9001CAPA

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. What they also left behind is a habit that is now the biggest untapped opportunity in many quality systems, namely that more gets recorded than gets acted on. The distance from record to action is shorter than most people reckon, and the gain already sits in the company’s own 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. It was the best answer of its time to the task, and it professionalised an entire generation of companies.

A system does, however, shape 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 more action is wanted, appealing to the staff rarely helps; the action has to be built into the system.

The standard led the way

The powerful part of the story is that the quality world learned its own lesson. The criticism arrived in the 90s, most sharply from John Seddon, who in 1997 argued that a certificate might at worst document no more than that the bureaucracy was working as intended. The standard responded with its biggest renewal to date. 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, where the weight falls on real control rather than ritual.

The message from 25 years of standards development is manageable enough: you may record less, but what is recorded has to lead to something. Read as a requirement it is a relaxation, and it is at the same time an occasion to tidy up.

"A measurement no one acts on is the storage of numbers. Give it an owner and an agreed reaction, and it starts working for the company."

— Prozanta Operations

First example: 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 the remark “adjusted”. The log is in order, while 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 out of production rather than merely filed. Twelve records have, in other words, become one action.

Second example: the complaints folder

The monthly report says seven complaints, the number gets a nod, and the meeting moves on. The number hides a pattern, though: 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. Seven complaints then stops being a figure to note and becomes 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.

Third example: the sheet on the wall

Consider the temperature log that has been filled in faithfully every morning for years. Ask what is supposed to happen when the number falls outside the limit, and the room often goes quiet. The fix is to give the measurement a reaction limit and an agreed action, such as stopping, checking and calling when the reading passes six degrees. If no reaction can be formulated, that is an honest signal that the measurement can be retired. Either outcome is a gain, since the measurement now either works or has freed up time.

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 anything having been changed 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 a deviation can get an owner the same day. That is where quality is decided, rather than at the annual audit.
  • •Anchor it: Follow up on whether actions close on time and whether the same deviations become rarer over time. That is the real test, and it only holds if the follow-up itself has become a routine rather than 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 and never as an accusation against the individual, because the problem is rarely the employees. The manager who says thank you for an uncomfortable record gets honest data for a long time afterwards. Everything above rests on that behaviour, and the culture follows once management leads through action.

✓The most important takeaways

  • →The systems of the 90s built the discipline, and the job today is to build the action on top of a foundation that has already been paid for.
  • →Record less, and act on what is recorded. Every measurement has to be able to answer who does what when it shows red.
  • →Recurring deviations are the best-documented improvement opportunities a company has, and the patterns are already in the logs.
  • →Start with the mapping. One honest question about when a record last led to an action shows exactly where the work should begin.

Going through the records and finding the ones that never lead to action is in practice a mapping of where the 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

  1. Seddon, J. (1997). In Pursuit of Quality: The Case Against ISO 9000. Oak Tree Press.
  2. BSI Group — The history and future of ISO 9001 (whitepaper).
  3. Deming, W. E. (1986). Out of the Crisis. MIT Press.
  4. Juran, J. M. & De Feo, J. A. (2010). Juran’s Quality Handbook (6th ed.). McGraw-Hill.
  5. American Society for Quality — ISO 9001:2015 (ASQ knowledge resource).

The references show the professional basis. Sources are reproduced in their original language.

Get the next insight in your inbox

1-2 educational articles a month on Lean, OEE and anchored operations. Only knowledge you can use.

No spam. Unsubscribe at any time. See our privacy policy.

From insight to action

Do you recognise the pattern in your own operations?

An initial conversation, no obligation. We map your situation and tell you honestly whether — and how — there is something to gain.