The Control System You Inherited Was Built to Report, Not Govern
Reporting and governing are two different jobs. Most operators inherit a system built for the first and spend a career feeding it, while the thing it was supposed to describe quietly drifts.
Somewhere in your operation there is a meeting that goes well.
The pack is clean. The metrics are green, or green with a small number of ambers that each have an owner and a date. The actions from last time are closed. Someone walks the room through the slides, the room nods, a few sharp questions get asked and answered, and the meeting ends on time. Everyone leaves with the same quiet sense that the thing is under control.
That meeting is the most dangerous artifact in your business. Not because it lies. Because it doesn’t have to.
I want to make an argument that took me an embarrassingly long time to arrive at, even with the word control in my title for most of my career. The control system most operators inherit was not built to govern the business. It was built to report on it. Those are two different jobs. A system can do the second one beautifully for years while quietly stopping doing the first, and nobody will notice, because the only thing anyone looks at is the report.
A system produces what it was designed to produce
Deming had a line that I think is the most useful sentence in management, and also the most ignored. Every system is perfectly designed to get the results it gets.
Read slowly, it’s almost aggressive. It says the results are not an accident. They are not a motivation problem, or a talent problem, or a this-quarter problem. They are the output the system was built to produce, running exactly as designed. If you don’t like the output, the system is not failing. It is succeeding at something other than what you assumed it was for.
Now apply that to your reporting.
Your management reporting system produces clean packs and green dashboards. Reliably. Month after month. By Deming’s logic, that is not a happy side effect. That is the output the system was designed to produce. Somewhere in its history, every incentive, every cadence, every template, every escalation rule got shaped — deliberately or by drift — toward one result: a meeting that goes well.
And it works. The pack is clean because producing a clean pack is what the system is for.
This is the trap, and it does not look like a trap, because the system is performing. The dashboards update. The reviews happen. The actions close. Every visible sign says the apparatus is healthy. The apparatus is healthy. It is doing its job. Its job was never to keep you in control. Its job was to produce the report.
Reporting and governing are not the same job
Let me separate the two jobs cleanly, because most of the confusion lives in treating them as one.
