Somewhere in your organization right now, a problem that used to generate a complaint has stopped generating one — not because it was solved, but because whoever noticed it stopped believing it was worth reporting.
Somewhere in your organization right now, a problem that used to generate a complaint has stopped generating one. Not because the problem was solved. Because whoever used to notice it stopped believing that reporting it would change anything. Silence is not a null result. It has to be actively verified as meaning “no problems” rather than passively accepted as meaning that, because the second interpretation is always cheaper to believe and frequently wrong.
How silence gets manufactured
The mechanism is simple and almost never malicious. Every report that goes nowhere teaches the person who filed it that reporting doesn’t work. It only takes a handful of those lessons before the flow of reports drops — not because conditions improved, but because the organization has quietly trained people out of reporting. Leadership then reads the resulting silence as evidence of health, because a quiet dashboard is easier to read that way than to interrogate.
The same pattern shows up on the customer side. A declining complaint count gets treated as a headline win in most customer-facing functions, when it is at least as often evidence that customers have concluded complaining is not worth their time. And it shows up in employee relations the same way — fewer formal grievances read as a healthier workplace, when it can just as easily mean people have concluded that HR does not act on what gets reported.
The test that actually distinguishes the two
There is one honest question that separates earned silence from manufactured silence: can you name a specific, recent instance of someone escalating a real problem and having it visibly acted on? Not a policy that technically allows escalation — an actual instance, recent, with a name attached, where raising something changed what happened next.
If you can name one easily, your silence is more likely earned — people are quiet because there is genuinely less to report, and they trust that if there were something, it would move. If you cannot name one, or if the example you land on took real effort to recall, the silence in front of you is more likely manufactured, and the clean dashboard is measuring how well people have learned to stop bothering you rather than how well the organization is actually running.
A second, sharper version of the same test works anywhere you have more than one related metric: has more than one number moved in the same direction, or only the one that was easiest to stop generating? Genuine improvement tends to show up in several places at once — fewer complaints alongside rising retention, fewer grievances alongside improving engagement. A silence-driven decline usually shows up in exactly one metric, the one people can quietly stop feeding, while everything connected to it stays flat.
The reader’s application
Do not wait for the next report to come in on its own. Go solicit the complaint that did not get filed. Ask a frontline team, directly and specifically, what they have stopped bothering to escalate. Treat any answer — even a small one — as more informative than another quarter of comfortable silence. Then check whether a second, related metric is confirming the good news or quietly contradicting it.
A quiet number earned through real improvement and a quiet number earned through abandonment look identical on a dashboard. They are not identical anywhere else. Trust what’s tested. Not what’s told — and silence is one of the most convincing things your organization will ever tell you.
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.
