your quality manual is not your quality system

Most organizations have a quality manual, a set of procedures, a documented system that describes how quality is supposed to work. And most organizations also have the way quality actually works, the real practices, habits, and decisions that happen on the floor every day. In a healthy operation those two things are the same. In a great many operations they are not, and the gap between the documented system and the practiced one is where problems hide, where audits get quietly survived, and where a company fools itself about how good it really is.

two systems, one on paper

The documented quality system is a description of intent. It says what should happen: this check gets done, this record gets kept, this reaction follows that trigger. The practiced system is what people actually do when they are busy, under pressure, and using the judgment they have built over years. Sometimes the practiced system is worse than the document, corners cut that the procedure would not allow. Sometimes it is better, informal knowledge and shortcuts that make the real process more capable than the written one. Either way, the moment the two diverge, the manual stops describing your operation and starts describing a fiction that everyone has agreed to maintain.

the manual nobody reads

A telling sign is how many people in an operation have actually read the quality manual that supposedly governs their work. In a lot of places the honest answer is almost nobody, outside of the people who wrote it and the auditor who checks it. The operators run to what they were shown and what experience taught them. The engineers run to what works. The manual sits in a system somewhere, updated when an audit approaches, referenced by almost no one in the actual doing of the work. A document that governs the work only in theory is not a quality system. It is a description of one, and the difference matters enormously.

why the gap is dangerous

When the document and the practice diverge, you lose the thing the system was supposed to give you: reliability that does not depend on individuals. The written system is what lets a new person do the job correctly, what lets you know a process will run the same way next month, what an auditor relies on to conclude you are in control. When the real system lives in people's heads and habits instead, none of that holds. The new hire inherits the manual, which is not how the work is actually done, and learns the real way through trial and error if they are lucky. The knowledge that actually runs the operation is undocumented and walks out the door when people do.

audits measure the wrong system

This gap is also why a company can pass audits and still have quality problems. The audit checks the documented system, and the documented system can be immaculate. What the audit struggles to see is the distance between that document and what actually happens when nobody is watching. A well-run audit will probe for it, but the fundamental design of a conformance audit is to check whether you do what you say, and if what you say lives in a manual disconnected from the floor, the audit is measuring a system that is not really the one making your product.

close the gap in both directions

The fix is not to write a thicker manual. It is to make the documented system and the practiced one the same thing, and that runs in two directions. Where the practice is worse than the document, you have a discipline and capability problem to close. Where the practice is better than the document, quietly, through informal knowledge, you have valuable reality that needs to be captured before it leaves with the people who hold it. A real quality system is one where the document describes what actually happens and what actually happens follows the document, so that the two are simply one thing. Anything less is a manual pretending to be a system.

How far apart are your documented system and the way the work actually gets done? And which one would a new hire actually inherit?