Listen to how your team describes its last miss. Two sentences will tell you more about your actual culture than any survey you have ever run.
Listen to how your team describes its last miss. Two sentences will tell you more about your actual operating culture than any engagement survey you have ever fielded — and unlike a survey, the two sentences can’t be gamed by someone who knows what answer is expected.
The claim
I have used a version of this test on an operating floor for years — walking into a unit unannounced and reading, in the first few minutes, how the room talks about its own recent performance. What I want to do here is generalize the same signal beyond the physical floor visit, because it works just as well in a normal team meeting, a post-mortem, or an ordinary conversation about a recent setback, and most leaders have access to that version of the test every single week without needing to travel anywhere.
The two sentences to listen for
The first sentence is how the miss gets named. Passive voice and diffused ownership — “the target was missed,” “timelines slipped” — signal a culture where nobody in the room owns the outcome. A named decision and a named owner — “I pushed the launch date and that was the wrong call” — signal a culture where ownership has actually been built into how people talk, not just into the org chart.
The second sentence is what happens immediately after the first one. Does the conversation drift toward blame-adjacent territory — who else was involved, what conditions made it hard — or does it move directly to what changes going forward? The direction of that second sentence tells you whether the room’s instinct, under real conditions, is to protect itself or to fix the thing.
I have applied this to my own account of a specific miss more than once, and the honest version of the test cuts both ways: the same discipline that lets you hear the gap in someone else’s two sentences should be turned on your own account of a failure before you trust it. “Accountable, not responsible” is not a standard you get to apply only to other people’s sentences.
Why this beats a survey
A survey measures what people are willing to say about culture in an anonymous, low-stakes moment, months removed from any specific event. This test measures what people actually do with a real, current, specific miss, while it still has real stakes attached — and that is a fundamentally stronger signal, because it cannot be gamed the way a survey response can be. Nobody has ever answered an anonymous survey by describing exactly how they intend to respond to their next failure. Everybody reveals it, unintentionally, the next time they actually have one.
The reader’s application
Do not manufacture a miss to test this on. Wait for the next real one — there will be one soon regardless of how well the team is performing — and listen, without commenting or steering the conversation, for the two sentences. Write down exactly what you heard before discussing it with anyone else, so you are recording the actual language rather than your interpretation of it after the fact.
Trust what’s tested. Not what’s told — and you can hear which one you have in under thirty seconds, the next time something in your organization actually goes wrong.
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.
