Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Had to Make a Quick Decision Question
Transcript
- Lucas: Alright Luna, let's talk about a question that shows up in almost every interview process at some point: 'Tell me about a time you had to make a quick decision.' Luna: And it's one of those questions that can feel really high stakes, because you're being asked to think on your feet about a time you thought on your feet. Lucas: Exactly. And the temptation is to either pick some dramatic story like 'I had to decide whether to call 911' or to play it safe with something trivial like 'I picked the blue font over the green one.' Both miss the point. Luna: So what is the point? What are they actually testing you on? Lucas: They're testing your judgment under uncertainty. They want to see if you can make a decision with incomplete information, take responsibility for it, and handle the outcome. It's not about speed for speed's sake. Luna: Right. In fact, I remember a hiring manager once told me that a great answer to this question is one where the candidate acknowledges the trade-offs they had to weigh in the moment. Lucas: That's a good point. A quick decision isn't just a snap decision. It's a decision where you consciously evaluate your options at speed. The best stories show that you had a framework in your head, even if you didn't have time to write it down. Luna: So what does a bad answer look like? Give me a concrete example. Lucas: A bad answer is when someone picks a story that's either too small or too big. Too small, and it feels like you're avoiding the question. Too big, and it feels like you're exaggerating or that you're a liability. I once heard someone say they had to decide whether to restart a server during a major outage. That's actually a good story, but they told it in a way that made them sound like they were just guessing. Luna: Guessing is the keyword there. They need to show that they had a method, not just luck. Lucas: Exactly. And that's where the STAR method comes in, but with a twist. Normally you do Situation, Task, Action, Result. For this question, you need to emphasize the 'Why now?' and the 'What could have gone wrong?' Luna: So the Situation should be set up to show the time pressure. Like, 'It was 4:30 PM on a Friday and the client needed a proposal by 5 PM, but we were missing a key piece of data.' Lucas: Perfect. That gives the interviewer a clear sense of stakes and timeline. Then the Action is where you show your decision-making process. You don't have to spell out every option, but you should mention the one alternative you rejected and why. Luna: And the Result? What makes a good result? Lucas: A good result is specific and shows impact. It doesn't have to be a heroic save. It could be that the decision saved the team an hour of rework, or that it led to a small but measurable improvement. The key is to show that your quick decision made a difference. Luna: I want to bring in a real-world example that I think illustrates this well. There's a story about an ER doctor who had to decide whether to start a risky procedure on a patient without full test results. She later said she based her decision on her training, the patient's visible symptoms, and the fact that waiting would be worse. That's a high-stakes version, but the structure is transferable. Lucas: Absolutely. And you don't need to be an ER doctor to use that structure. In a marketing role, maybe you had to decide whether to launch a campaign with a typo in it because fixing it would miss the campaign deadline. You weigh the risk of looking unprofessional against the cost of missing a key sales window. You choose, and you explain why. Luna: And what if the decision didn't turn out well? Can you still use a story where the outcome was negative? Lucas: You can, but it's riskier. If you use a negative outcome, you need to be very clear about what you learned and how it changed your approach. That can actually be more powerful because it shows self-awareness and growth. But I'd only recommend it if you have a really strong 'what I'd do differently' ending. Luna: That makes sense. Let's talk about the common pitfalls. What are the top mistakes people make when answering this question? Lucas: First, picking a story that's not relevant to the job. If you're interviewing for an accounting role, talking about a time you made a split-second decision on a hiking trip might not resonate. It doesn't have to be work-related, but it should show transferable skills. Luna: Second, forgetting to mention the outcome. I've heard so many answers that end with 'and that was it.' You need to close the loop. Lucas: Third, rambling. This is a question where interviewers are also noting how you handle pressure in the moment. If your answer meanders, it undermines your message. Aim for 90 seconds max. Luna: So structure is huge. Let's give listeners a mini-template they can use. Lucas: Sure. Start with the situation in one or two sentences, making sure to establish the time constraint. Then state the task or the goal you were trying to achieve. Then the action: describe the decision you made and the one alternative you considered. Then the result: what happened, and if possible, a number or a concrete improvement. Luna: And maybe add a reflective line at the end, like 'That experience taught me to trust my instincts but also to double-check my assumptions when I have a moment.' Lucas: Exactly. That shows you're not just a reactor, you're a learner. Now, let's talk about how to prepare this before the interview. You can't think of a good story on the spot, so you need to have a few ready. Luna: How many should you have? I've heard different advice. Lucas: I'd say at least two or three solid stories, each a different flavor. One from work, one from a project or volunteer role, and maybe one from a personal situation if it's compelling. That way you can adapt to the specific job. Luna: And they don't all have to be high-octane. Sometimes a simple story, like deciding to switch vendors mid-project, can be perfect because it shows analytical thinking. Lucas: Right. And that also brings up the importance of tailoring your story to the job description. If the role emphasizes collaboration, maybe your quick decision involved consulting a colleague before acting. If it's a fast-paced startup, focus on speed and adaptability. Luna: I want to add a tip I learned from a former boss: practice your story out loud, but don't memorize it word for word. You want to sound like you're telling it for the first time, not reciting from a script. Lucas: That's a great point. And a side benefit of this question is that it's one of those where you can actually show your personality. A little humility or a touch of humor can go a long way, as long as you stay professional. Luna: Before we wrap up, I think it's worth mentioning something that's been on my mind. This podcast is ad-free, and that's only possible because of the listeners who support us. Lucas: Yeah, that's true. A couple of dollars a month genuinely makes a difference. If you've gotten value from these episodes, you can support us at buy me a coffee dot com slash fexingo. It helps us keep doing this. Luna: And we really appreciate it. Now, back to decisions. One last piece of advice? Lucas: Yes. Remember that the interviewer isn't looking for a perfect decision. They're looking for a thoughtful one. So choose a story that shows you can navigate ambiguity and take ownership. That's what sets you apart. Luna: And if you're listening and you have an interview coming up, take five minutes today to write down one of your own quick decision stories. It'll be there when you need it. Lucas: Good luck out there. We'll be back next week with another common interview question, so subscribe if you haven't already.