Every organization has two versions of its own performance: the one that gets reported upward, and the one that would survive being tested. Most leaders stopped checking which one they were looking at.
Every organization has two versions of its own performance. One is the version that gets told upward — in the report, the briefing, the confident answer in the hallway. The other is the version that would actually survive being tested. They are not always the same version, and most leaders have quietly stopped checking which one they are looking at.
The claim
Executive communication runs almost entirely on assertion. Reports, dashboards, briefings, confident answers to direct questions — all of it is telling. Verification is rarer, slower, and less comfortable, because testing something means accepting the possibility that the answer comes back wrong. Organizations default to trusting the assertion because the assertion is free and the test costs something. That default is the actual risk, and it is almost never named as one.
Why telling is cheaper than testing
An assertion costs the person making it almost nothing to produce. A confident answer takes the same amount of time to say as an uncertain one. Testing the assertion costs the person doing the testing real time, real political capital, and the real risk of surfacing a problem that nobody in the room wanted found today. The economics favor telling every single time, unless someone with authority deliberately overrides them.
This is not a story about dishonesty. Most of the assertions running through any organization are made in good faith, by people who believe them. The problem is not that people lie about their numbers. The problem is that nobody has built in a habit of finding out whether the numbers would hold up if someone actually checked — and an organization can run for years on unverified good-faith assertions before the gap between what is told and what is true becomes expensive.
The sentence that tells you which one you have
There is a specific test I have used for thirty-six years to sort a responsible answer from an accountable one, and it works just as well for sorting a told claim from a tested one. Ask someone to describe a specific outcome they own that did not go well. Then listen for one sentence: “I will not make any excuses. It is my fault we failed.”
“I will not make any excuses. It is my fault we failed.”
Almost anyone can tell you they are accountable. Far fewer can produce that specific sentence, unprompted, about a specific failure, without redirecting some of it toward a teammate, a market condition, or bad timing. The sentence is not a script to memorize. It is a diagnostic, because it is very hard to say convincingly if it is not true — and very easy to detect when someone is reaching for a version of it that protects them instead.
That is the entire distinction between telling and testing in one small example. A resume tells you someone is accountable. A specific question about a specific failure, listened to carefully, tests it.
What testing actually looks like at scale
The same principle scales past individual conversations. An operations review that samples a specific claim — pulls the underlying data, walks the actual process, asks the person closest to the work to describe it without notice — is testing. An operations review that accepts a summary slide and asks whether there are any concerns is telling, dressed up in the format of oversight.
A reference check that asks for a specific story, with names and outcomes attached, is testing. A reference check that asks whether the candidate is a strong leader is telling — nobody has ever answered that question with anything other than yes.
The reader’s application
Pick the single most important assertion currently driving a decision on your desk. Not the least important one — the one carrying the most weight. Design one specific, low-cost way to test it this week, rather than accepting it because it was delivered with confidence. You do not need an audit team or a consultant. You need one specific question, asked of the right person, about a specific instance rather than a general claim.
Do this once, on the assertion that matters most, and you will find out quickly whether your organization has been giving you tested answers or told ones. Trust what’s tested. Not what’s told.
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.
