When your audit produces perfect scores for years running, the audit has stopped working. Here is how to see it, and what to do about it.
For three years, the audit produced zero failures. The institution’s conclusion was that we no longer needed to run it. My conclusion was the opposite. Zero failures over three years is not evidence the organization is ready. It is evidence the audit has stopped testing anything. We reinstated the discipline. The next cycle produced failures. That was the point.
Most boards, most Fortune 500 CEOs, and most operating partners are looking at a version of the same signal right now — a readiness review, a compliance audit, a safety report, an operations diagnostic — that has produced clean results for so long it has begun to feel obsolete. The obsolescence is real. It just does not mean what most executives think it means.
The mechanism
Any organization asked to grade itself will, over time, drift toward the answers that produce fewer consequences. This is not corruption. It is not laziness. It is the natural gravity of a self-assessment discipline embedded in incentive structures, career paths, and the everyday cost of speaking bad news up the chain. What starts as a rigorous test becomes, three or four years in, a script both sides know how to run.
The tell is not that the results are unbelievable. The tell is that they are boring. The variance disappears. Every quarter looks like the last quarter. Every function reports a green traffic light. Every function has an explanation for why the traffic light stays green even under conditions that should have produced yellow.
By the time the board is looking at that report, three things have happened that they cannot see. The people running the test have adjusted it to what the organization can pass. The people taking the test have adjusted their behavior to what the test can catch. And the institutional memory of what an actual failure looks like has faded to the point that recognizing one, in real time, has become harder than it used to be.
Zero failures is not the reward for a working discipline. It is the diagnostic signature of one that has stopped working.
The case I know best
An operating discipline I inherited had produced zero failures for a period long enough that the institution’s leadership was about to retire it in a formal review. The internal case for retirement was not a bad one. The discipline was disruptive. It cost operating hours. It generated paperwork. Every previous cycle had come back clean, and the operators on the receiving end were increasingly framing it as theater — a ritual we ran to demonstrate readiness rather than to test it.
I took the opposite view. Zero failures over the period in question was not evidence of readiness. It was evidence the discipline had adjusted to what the organization could pass, and the organization had adjusted to what the discipline could catch. Both sides were operating in good faith. Both sides had drifted in the same direction. The only way to know whether we were actually ready — not whether we were passing the test we had built for ourselves — was to reinstate the discipline in a form the organization could not predict.
We reinstated it. The next cycle produced failures. Specific failures, in specific units, on specific dimensions the retired version had stopped testing years earlier. Nobody was pleased about it. The findings produced hard conversations. Some careers took hits that would not have taken hits under the retired discipline. But the argument was clean. What we had been calling readiness was, in significant measure, the absence of a test that could detect the difference.
Three questions for your next board meeting
That story is not about one institution. It is about the decay pattern of any self-assessment discipline that runs long enough. If you sit on a Fortune 500 board, or run an operating partner practice, or hold a divisional CEO seat, you are looking at a version of it right now. Three questions.
First: name one operating review or audit that has produced clean results for six or more consecutive quarters. What has changed in what that review actually tests during those quarters? If nothing has changed, the review has probably drifted.
Second: when was the last time your safety, compliance, or quality report surfaced a finding that surprised the executive team? Surprise is the diagnostic. If nothing has surprised the executive team in a year, the reporting instrument is no longer measuring the same organization.
Third: if you retired the review tomorrow, would you know what to run in its place? If the honest answer is that you would replace it with a version that produces the same clean results, that answer is the finding.
Two civilian analogs make the same point. Budget variance reviews that report zero variance for six quarters are diagnostic of a variance-reporting discipline that has stopped tracking variance. Safety incident reports that report zero recordable incidents for three years running are diagnostic of a reporting discipline that has stopped registering incidents that would have been recorded five years ago.
The prescription
Identify one test your organization has quietly retired — retired formally by decision, or retired informally by drift. Reinstate it. Run it in a form the organization cannot predict. Watch what the first cycle produces.
The first cycle will produce findings. Some will surface capability gaps the organization did not know it had. Others will surface the fact that people currently in seats have been operating without the discipline the seat requires. Both categories are useful, and both are the point of running the reinstated test.
Do not, under any circumstances, use the results of the first cycle to punish. Use them to reset the daily standard. Then run the reinstated discipline again in two quarters and watch what changes.
Readiness is not a lagging indicator you can measure after the pressure event. It is a leading indicator you have to test for on any given Tuesday. What you tolerate, you teach. What you enforce, you build.
Scott Pleus is an operating executive who has built his career on a single conviction: an organization’s confidence in its own readiness is only as good as the last time someone actually tested it. If nobody told you your numbers were good, would you still believe them? That conviction was forged over three decades of command in the United States Air Force, retiring as a Lieutenant General and the longest-serving Acting Vice Chief of Staff in the role’s 79-year history. His command experience is the civilian equivalent of running large, high-consequence operations at every level of scale — from a single division, to a joint international operation, to the number-two position in a 680,000-person global organization. In every one of those roles, the product was readiness, and there was no such thing as a plausible excuse for being wrong about it. His standard, in his own words: accountable, not responsible. That is the experience most executive backgrounds don’t have, and it is what any organization needs when it wants to know — not hope — that it can perform under pressure. Early in his career, he noticed something worth learning from: a self-assessment that had never once produced a failure. Rather than take that as good news, he treated it as a signal that the test itself needed to evolve. He built a new version of the check — one that measured real readiness instead of rehearsed readiness — and kept refining it, even when the organization pushed back, because he was committed to the standard underneath it, not just the version of it that was easiest to pass. That same instinct shaped how he led. He made a habit of showing up unannounced, not to catch anyone, but to see the organization as it actually ran day to day — and to ask the one question a prepared briefing never answers. That habit paid off when he inherited a struggling unit: he gave its two senior leaders a clear deadline and clear ownership of the turnaround, and in sixty days, the unit had rebuilt the standard for itself. The stakes in his operating environment left no room for a wrong answer — there was no version of a readiness failure that was merely inconvenient. That is precisely why the discipline transfers: an executive who has enforced a verification standard with zero margin for error brings a rigor to operating risk that most executive backgrounds never have to develop. Trust what’s tested. Not what’s told.
