I used to ask candidates to describe their greatest strength and weakness, walk me through their resume, and explain why they wanted the job. Standard questions, comfortable to ask, and in hindsight almost completely useless at predicting who’d actually perform well once hired. After tracking outcomes across a couple dozen hires over several years, one question stood out as a genuinely reliable predictor, and it wasn’t anything close to what I used to ask.
The Question: “Tell Me About a Time You Were Given Incomplete Instructions. What Did You Do?”
Not a hypothetical. A real, specific past situation, followed by genuine follow-up questions about exactly what they did next, not what they’d theoretically do in a similar situation. The answer to this single question correlated more strongly with actual on-the-job performance, across every role I’ve hired for, than any other single question I’ve asked in an interview.
Why This Specific Question Works So Well
Early-stage and small business roles are defined by ambiguity in a way that larger, more established companies with detailed processes and documentation often aren’t. Instructions are frequently incomplete, not because of poor management, but because the business itself is still figuring things out in real time, and a new hire’s actual, most valuable skill in that environment is often the ability to make reasonable, sound judgment calls without needing every detail specified in advance.
This question directly tests for that specific skill, rather than testing for general competence or enthusiasm, which is what most standard interview questions actually measure instead.
What the Best Answers Actually Sound Like
The strongest answers I’ve heard describe a specific real situation, name the actual gap in information clearly, and then walk through a genuine, sound reasoning process for how they filled that gap, what assumptions they made and why, who they checked in with if anyone, and what the actual outcome was, including any mistakes made along the way. Strong candidates aren’t afraid to admit an assumption turned out wrong, because what I’m evaluating is the reasoning process itself, not whether the outcome was flawless.
One candidate described being asked to “handle the vendor situation” with almost no context, figuring out through her own initiative which vendor was actually being referenced, making a reasonable judgment call about the appropriate response based on limited available information, and then proactively following up with her manager afterward to confirm she’d interpreted the ambiguous instruction correctly. That answer told me more about how she’d actually perform in my specific business than an hour of more conventional interview questions had for other candidates.
What Weak Answers Reveal, Just as Clearly
Candidates who struggle with this question tend to reveal one of two patterns, each genuinely useful to know before hiring. Some default to freezing, waiting for clarification rather than making any reasonable judgment call, which can be a real liability in an environment where clarification isn’t always readily available. Others default to acting without any real reasoning process behind the decision, unable to clearly articulate why they chose the specific path they took, which suggests a pattern of impulsive rather than genuinely judgment-based decision-making.
Both patterns are worth knowing about honestly before a hire, and neither shows up reliably in more conventional interview questions that don’t specifically probe for how someone handles genuine ambiguity.
Why I Stopped Trusting the Standard Questions
“What’s your greatest weakness” reliably produces a rehearsed, safe answer, since virtually every candidate has anticipated this exact question and prepared a polished response in advance. It measures interview preparation, not actual job performance. “Why do you want this role” measures how well someone can construct a compelling narrative on demand, a genuinely different skill than the skills the actual job requires day to day.
The incomplete-instructions question is much harder to prepare a polished, generic answer for in advance, because it requires recalling and honestly describing a specific real situation rather than reciting a rehearsed general answer, and that difficulty is exactly what makes it more reliably predictive.
How to Actually Use This in an Interview
Ask the question directly, then genuinely follow up. “What specifically was unclear? What did you decide to do, and why that specific approach? What happened as a result? Would you handle it differently now?” These follow-ups matter enormously, since a single surface-level answer doesn’t reveal nearly as much as a deeper conversation that traces the actual reasoning process.
Give the candidate real time to think of a genuine example rather than expecting an instant answer. A brief pause to recall an actual specific situation is a good sign, not a weakness, since it suggests they’re searching for a real example rather than reciting something rehearsed in advance.
What to Do Now
Add this question to your next interview, replacing at least one of the more conventional questions you’d normally ask. Push for genuine specifics with real follow-up questions rather than accepting a surface-level answer, and pay close attention to the reasoning process described, not just whether the eventual outcome happened to work out well.
This single question, asked properly with real follow-up, will likely tell you more about how a candidate will actually perform in an ambiguous, early-stage environment than the rest of a typical interview combined.
