One question, asked correctly, tells you more about a candidate’s operating standard than every reference check combined. Describe a specific outcome you own that failed. Then listen for one sentence.
One question, asked correctly, tells you more about a candidate’s actual operating standard than every structured reference check you will run combined: describe one specific outcome you owned that failed. Then stop talking, and listen for a sentence that either shows up or doesn’t.
The distinction, briefly
Responsibility is a duty statement — did you do what you were assigned to do. Accountability is an outcome statement — do you own what happened, regardless of cause. A candidate can meet every duty in a job description and still preside over a bad outcome without ever internalizing that the outcome was theirs. The interview question exists to find out which one you are actually hiring, because the resume will never tell you — resumes are written entirely in the language of responsibility.
How to ask it correctly
The question only works if you enforce three constraints. First, the candidate has to name one specific outcome, not a category of outcomes — “a time projects didn’t go well” is not an answer; “the Q3 launch we missed by six weeks” is. Second, the failure has to have genuinely been theirs to own, not their team’s or a predecessor’s — if they describe something that was clearly someone else’s call, ask again. Third, follow up on anything that sounds like it is distributing blame, even subtly, and watch whether the second answer sounds more or less accountable than the first.
Reading the answer
A responsible-but-not-accountable answer sounds like a list of contributing factors: the market shifted, another team was late delivering something they needed, the timeline was unrealistic from the start. Every one of those things might be true. None of them is the sentence you are listening for.
An accountable answer sounds different in a way that is hard to fake convincingly: “I will not make any excuses. It is my fault we failed.” It owns the outcome plainly, names what specifically changed in how they operate afterward, and does not perform contrition for your benefit. The difference between a candidate reciting something that sounds like ownership and a candidate who actually means it is usually audible within one follow-up question, if you’re listening for it rather than just checking a box.
What this predicts, and what it doesn’t
I want to be precise about what I’m claiming here. I am not telling you this question has been validated against a hiring database. I am telling you it is the single question I have found most useful, over three decades of putting people into seats where the cost of a responsible-but-not-accountable operator is high. It tests a real-time instinct under a small amount of real pressure, in the room, rather than a rehearsed narrative — and that is worth more to me than a longer battery of questions that never puts the candidate in a position to reveal anything they didn’t already plan to say.
The reader’s application
You will not screen your way to an accountable hire by asking about strengths, or by asking hypothetical questions about how they would handle a disagreement. You get there by asking about one specific, real failure, and listening — carefully, with one good follow-up ready — to what they do with it. Trust what’s tested. Not what’s told, and a resume is the most polished version of “told” you will ever be handed.
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.
