How to answer "How do you make decisions?" — show your process, not just your gut
"I go with my gut" is the most common answer to this question, and it's the weakest one — it tells the interviewer nothing they can evaluate. Decision-making is one of the few skills interviewers can actually probe in a single question, because a real process is describable in specific, repeatable steps. Vague confidence isn't a process. Here's a framework for showing yours.
What they're actually checking
Three things: judgment (do you weigh tradeoffs, or jump to conclusions?), calibration (do you know when to stop gathering information and act?), and ownership (do you communicate and stand behind decisions once made?). A strong answer covers all three by walking through how you actually work, not a philosophy of decision-making in the abstract.
The framework: Gather → Weigh → Commit
- Gather. What information and input you pull in before deciding — data, the people closest to the problem, real constraints. Specific sources, not "I do my research."
- Weigh. How you evaluate the tradeoffs once you have the inputs. Name an actual method: how reversible the choice is, how bad the worst case looks, what the deadline allows.
- Commit. How you know when to stop gathering and act, and how you communicate the decision afterward so nobody is surprised by it.
The "Weigh" step is what separates this from a vague answer. Anyone can say they consider the options. Naming the actual lens you use — reversibility, worst-case severity, time pressure — is what proves there's a real process behind it.
A worked example
"We had to decide whether to delay a launch by two weeks to fix a data-accuracy issue, or ship on schedule with a known caveat. I started by pulling in the people closest to the problem — the engineer who found the issue and the account manager who'd hear about it from customers first. Then I weighed it on two things: how reversible the choice was — shipping with the caveat was easy to walk back if it went badly, missing the committed date wasn't — and how bad the worst case looked, which was a wrong number in a report customers make real decisions from, not just a cosmetic bug. That made it fairly clear-cut, so we delayed. I told the executive sponsor why in one paragraph that same day, so nobody was surprised by it later."
Gather (the two people closest to it) → Weigh (reversibility and worst-case severity, named explicitly) → Commit (decided, then communicated it same-day).
Adjust the example to the level of the decision
Not every decision deserves the same process, and saying so is itself a sign of good judgment. A reversible, low-stakes call should be quick — over-processing a small decision is its own failure mode. Pick an example where the stakes matched the amount of process you describe, and say plainly that you scale the process to the decision. That single line does more to demonstrate judgment than any amount of detail on the framework itself.
Common mistakes to avoid
- "I trust my gut." With no process behind it, this sounds impulsive rather than experienced, however good your instincts actually are.
- One process for every decision. Presenting a heavyweight process as if it applies equally to a five-minute call and a six-month bet reads as rigid, not thorough.
- No real example. An abstract description of how you "generally" decide things is forgettable. A specific decision is not.
- Treating slowness as a virtue. Endless deliberation presented as diligence often reads as an inability to commit.
- Skipping the communication step. A decision nobody hears about until it's acted on undercuts the trust the rest of the answer is trying to build.
The bottom line
"How do you make decisions?" is really asking whether you have a repeatable process or just confidence. Name what you actually gather before deciding, the specific way you weigh tradeoffs, and how you commit and communicate once you've decided — matched to a real example at a stakes level that fits the process you describe. That's what turns "I go with my gut" into an answer an interviewer can actually evaluate.
Walk in with a process you can actually describe.
Slaydit helps you prep grounded, specific answers from your real experience — never generic, never invented.
Try Slaydit free →Related: What is your biggest professional regret? · How do you prioritize your work? · What is an AI interview copilot?