By Lee Flanagan
By Johnny Campbell, Co-founder & CEO, SocialTalent
Introduction
Decision making isn’t about being confident or fast. Watch someone describe a choice they made, and you’ll see something else entirely: do they lay out the trade-offs they weighed? Can they articulate what information they lacked and why it mattered? Do they acknowledge where the call could have gone differently—not from modesty, but because they actually thought about reversibility and blast radius? Sound judgement under uncertainty is decision making. A snap call delivered with conviction isn’t.
Most interviewers assess it badly. They judge the decision by its outcome—”did it work out?”—and miss the reasoning entirely. They ask “tell me about a difficult decision” and accept vague answers without probing: what exactly made you uncertain? What would have changed your mind? If you’d made the opposite call, what would the fallout have been? They conflate confidence with quality. They rarely ask how someone gathers incomplete information, who they consult, or when they’d hit pause rather than commit. Without those probes, you’re not assessing decision making. You’re watching performance.
This guide covers 20 interview questions across 5 dimensions: Decision Quality Under Uncertainty, Reversibility & Blast-Radius Thinking, Trade-off Articulation, Business Acumen and Intuition. All are designed to expose the reasoning, not the outcome.
Decision Quality Under Uncertainty
What good looks like
A strong decision-maker can act when the information is incomplete, conflicting, or time-pressured, and can separate the quality of the decision from the quality of the outcome. They are explicit about what they knew, what they assumed, and what they did to reduce uncertainty before committing.
Behavioural questions
- Tell me about a decision you had to make without the information you wanted.
- What were you actually missing? Data, a stakeholder view, a precedent?
- What did you do to close the gap before you committed, and what did you accept you’d never know?
- How did you weigh the cost of waiting against the cost of moving?
- When did you make the call, and what happened in the weeks after?
- Tell me about a decision you got right where the outcome looked wrong, or vice versa.
- What was the decision and what did you base it on at the time?
- What separated the decision quality from the outcome quality in your head?
- Who else saw it the way you did, and who didn’t?
- What did you take from it that changed how you decide now?
- Tell me about a time you changed your mind on a decision you’d already made public.
- What was the new information that moved you?
- How did you communicate the reversal, and to whom first?
- What did it cost you — credibility, time, money, something else?
- How long after the original call did the change happen?
Situational scenario
You’re three weeks into a project with a hard external deadline in six weeks. A senior colleague flags a risk you hadn’t considered — they think there’s maybe a 30% chance it derails the project entirely. Investigating it properly would cost you a week. Ignoring it and being wrong would cost you the deadline.
Talk me through how you’d handle that.
Then introduce a constraint: “Your sponsor tells you informally they think the colleague is overstating the risk and you should press on. Does that change your call?”
What to listen for
whether they try to cheaply de-risk before committing a full week, how they weight a senior view against a quantified risk, whether they articulate a threshold for what would make them stop, and whether they distinguish between the sponsor's authority and the sponsor's evidence.
Reversibility & Blast-Radius Thinking
What good looks like
A strong decision-maker categorises decisions by how reversible they are and how far the consequences spread, and they calibrate the rigour of their process to match. They move quickly on small, reversible calls and slow down deliberately on decisions that are hard to unwind or affect people beyond their immediate team.
Behavioural questions
- Tell me about a decision you made quickly that you’d have made differently if you’d known how far it would spread.
- What was the decision and who did it ultimately affect?
- At the point you made it, who did you think it would affect?
- What was the unwinding cost when you realised the scope?
- How long did it take to fully reverse, or did you?
- Tell me about a decision where you deliberately slowed yourself down.
- What was it about this one that made you treat it differently?
- What extra steps did you add to your process?
- Who did you bring in that you might not normally have?
- What was the outcome relative to decisions you’d made at your usual speed?
- Tell me about a one-way door decision you’ve made — something you couldn’t unwind.
- How did you know it was one-way at the time, or did you only see that afterwards?
- What did you do to stress-test it before committing?
- Who signed off, and what was their role in the call?
- What’s the test you’d use now to spot a one-way door earlier?
Situational scenario
You’re being asked to approve two changes on the same day. The first is a pricing change for a small customer segment — easy to revert if it goes wrong. The second is a restructure of how two teams report into each other, which would be socially and politically painful to undo within six months.
How would you approach each of them differently?
Then introduce a constraint: “Your manager wants both decided by end of week because they're going on leave. What do you do?”
What to listen for
whether they explicitly name reversibility as the variable that changes their process, whether they're willing to push back on the timeline for the harder-to-reverse call, how they think about who needs to be consulted in each case, and whether they treat "my manager is away" as a reason to lower or raise the bar.
Trade-off Articulation
What good looks like
A strong decision-maker can name what they are giving up, not just what they are choosing. They make the cost of a decision visible to stakeholders, resist framing choices as obvious or risk-free, and hold the tension when more than one option has real merit.
Behavioural questions
- Tell me about a decision where you had to choose between two options that both had a strong case.
- What were the actual two options on the table?
- What did each one cost you that the other didn’t?
- How did you communicate the trade-off to the people affected?
- Looking back, was the option you didn’t pick stronger than you gave it credit for?
- Tell me about a time you had to push back on a stakeholder who wanted both.
- What were the two things they were asking for, and why couldn’t you do both?
- How did you frame the trade-off for them?
- Where did you end up landing, and who made the final call?
- What would you do differently in that conversation now?
- Tell me about a decision where the trade-off only became clear after you’d committed.
- What did you think you were trading off at the time?
- What did the real trade-off turn out to be?
- When did you realise, and what did you do about it?
- How has that changed how you scope decisions now?
Situational scenario
A stakeholder wants you to ship a piece of work two weeks early. You can do it, but it means cutting either a quality check that would catch some edge cases, or a smaller feature that one specific customer has been asking for. They’re insisting both are non-negotiable.
How do you handle the conversation?
Then introduce a constraint: “They escalate to your manager, who tells you to find a way to do all three. What do you say?”
What to listen for
whether they make the trade-off concrete with specifics rather than abstract trade-off language, whether they put the choice back on the stakeholder rather than absorbing it themselves, how they handle the escalation without either capitulating or digging in, and whether they distinguish between "I can't" and "the cost is X — do you want to pay it?".
Business Acumen
What good looks like
A strong decision-maker reasons commercially. They understand how their decisions affect revenue, cost, margin, and risk, and they can put rough numbers on those effects rather than reasoning purely qualitatively. They can read a P&L view of their own work and pick the option that’s right for the business, not just the option that’s right for their function.
Behavioural questions
- Tell me about a decision where you had to weigh revenue against cost or risk.
- What were the numbers actually in play — order of magnitude is fine?
- How did you build out the commercial picture? Did you do the maths yourself or get it from someone?
- What assumption in that calculation were you least sure about?
- What did the outcome look like against your estimate?
- Tell me about a decision you made that looked right operationally but you’d argue was wrong commercially, or vice versa.
- What did each lens tell you?
- Which one did you weight more heavily, and why?
- Who was holding the other view at the time?
- How would you decide it now?
- Tell me about a time you spotted a commercial implication that the people around you had missed.
- What was the implication, and how did you spot it?
- How did you raise it, and how was it received?
- What changed as a result, if anything?
- How long between you flagging it and the decision being revisited?
Situational scenario
You’re choosing between two options. Option A brings in roughly £200k in new revenue this year but requires hiring a person to deliver it, costing about £80k fully loaded plus management overhead. Option B saves about £120k by retiring a tool no one’s particularly attached to, but locks you out of a customer segment your sales team thinks might be worth chasing next year.
Which way do you lean, and what would change your mind?
Then introduce a constraint: “Finance tells you the £200k revenue figure is the optimistic case — the realistic case is closer to £130k. Does that change your call?”
What to listen for
whether they handle the numbers without bluffing, whether they reason about net contribution rather than just top-line revenue, whether they treat the sales team's forecast on the new segment as data or as a vibe, and whether they ask sensible questions about the inputs rather than over-committing to a clean answer.
Intuition
What good looks like
A strong decision-maker can act on incomplete information using pattern recognition built from experience, and they can articulate where that intuition comes from rather than presenting it as a hunch. They know when their gut is calibrated and when it isn’t, and they have a track record of testing intuitive calls against evidence rather than defending them.
Behavioural questions
- Tell me about a decision you made on instinct that turned out to be right.
- What were the signals you were picking up on, even if you couldn’t articulate them at the time?
- What patterns from your experience were you matching against?
- What would you have done if you’d had time to analyse it properly — same call?
- How long after the decision did you know you’d got it right?
- Tell me about a time your gut was wrong.
- What did your instinct tell you, and what did the evidence turn out to be?
- Where do you think the bad pattern-match came from?
- What were the warning signs you missed or dismissed?
- How has that changed what you trust your gut on now?
- Tell me about a decision where you ignored the data because something felt off.
- What was the data telling you?
- What was the “off” thing — a person, a number, something unspoken?
- How did you check whether your instinct was worth acting on?
- What happened, and what did you learn about your own calibration?
Situational scenario
You’re interviewing a candidate who looks excellent on paper and has given strong answers to every question. Two of your colleagues want to hire. You have a nagging sense that something isn’t right, but you can’t point to a specific answer or moment that’s bothering you.
What do you do?
Then introduce a constraint: “You can't get any more interview time with the candidate, and the team needs the hire urgently. Final call?”
What to listen for
whether they try to surface the specific pattern their gut is responding to rather than just defending the feeling, whether they distinguish their intuition from bias, whether they're willing to overrule colleagues on a feeling, and whether they treat "I can't articulate it" as a reason to investigate further or as a reason to discount it.
How to Use These Questions in a Structured Interview
These questions work best as part of a structured interview where you calibrate scoring beforehand. Use a 1-to-5 rubric: 1 is reactive and confidence-driven; 3 is sound process with visible reasoning; 5 is reflective, calibrated, and aware of constraints. Don’t score the answer based on the first five minutes. Your follow-up probes matter more.
When you hear an answer, push into three areas: the actual constraint or uncertainty they faced (not a cleaned-up version), the specific reasoning they’d apply again, and what would make them change their mind. Ask “what would you do differently if you ran that forward again?” If they flinch or offer vague adjustment, the decision-making process wasn’t sound. If they get specific and honest, you’re watching real judgement.
The second critical move: calibrate across interviewers. Record your rubric definitions, score independently, then compare. You’ll spot where one interviewer accepts any answer with confidence, or where another is too harsh on candidates who chose differently than they would. Bias detector tools can flag some language patterns in your questions beforehand, and Interview Intelligence can flag inconsistency across your team.
See how Interview Intelligence solves this →
Check your interview questions for biased language →
Ready to Assess Decision Making at Scale?
Frequently asked questions
How do I score a decision if the outcome was actually bad but the reasoning was solid?
You score the decision-making process, not the luck. A candidate might reason beautifully through a choice that markets or circumstances invalidated. Separate those. Ask whether they'd make the same call again with the information they had then—not whether it turned out well.
What's the difference between decision making and problem-solving?
Problem-solving is diagnosis. Decision-making is choice under uncertainty. You can solve a problem perfectly and still make a poor decision about what to do with that solution. These questions focus on the choice part.
Should I expect different answers for senior versus junior hires?
Yes. A junior hire might describe consulting someone before deciding; a senior hire should describe knowing when not to. A junior hire shows sound reasoning; a senior hire shows calibrated reasoning and awareness of their own blindspots. Recalibrate the 1-to-5 rubric for the level you're hiring.
Can I use these questions for remote interviews?
Absolutely. The same probing works. You might find remote candidates give slightly more polished answers because they've had time to prepare. Dig harder into the detail and the moment of uncertainty. Ask them to walk you through their thinking in real-time rather than giving you the summarised version.
How many of these should I ask in one interview?
Two to three. You want time to follow up, probe, and score. A single hour with three decision-making questions gives you a far clearer picture than six rushed questions with surface-level answers.