Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / Handling the Tell Me About a Time You Had to Make a Quick Decision Question
Transcript
- Lucas: So today we're tackling a question that doesn't get as much airtime as 'tell me about a time you failed' or 'tell me about a time you showed initiative' — but it shows up in interviews a lot. It's the 'tell me about a time you had to make a quick decision' question. And the reason it's so sneaky is that it's not really about speed. It's about judgment under ambiguity. Luna: That's such a good point. I've seen candidates freeze on this one because they think the interviewer wants to hear that they're impulsive. But that's totally wrong. Lucas: Exactly. And to make that concrete, let me tell you about a hiring manager I talked to — she runs operations at a mid-sized logistics firm here in Chicago. She told me she asks this question in nearly every interview she does, and she's looking for one specific thing: can you separate the signal from the noise when the clock is ticking. She gave me an example of a great answer she heard recently. Luna: Oh, I want to hear this. Was it someone in logistics, or a different function? Lucas: It was a candidate for a supervisor role. The story was about a delivery route that got hit with an unexpected road closure. The candidate had to reroute a dozen drivers in about twenty minutes, while also juggling a customer complaint and a driver calling in sick. The candidate didn't just talk about what they did — they walked through how they prioritized. They quickly assessed which deliveries were time-sensitive, which drivers had the most flexibility, and they reassigned the sick driver's load to a less senior employee who had done that route before. They also set up a quick call to the complaining customer to buy themselves time. Luna: That sounds like a textbook answer. What made it stand out to the hiring manager? Lucas: She said it was the structure. The candidate didn't say 'I made a decision and it worked out.' They walked through their mental checklist. She told me that's the difference between someone who just reacts and someone who makes a decision. A reaction is instinctive; a decision is a mini-process. And that's what she's trying to uncover. Luna: Right. So what's the actual framework that makes a good answer? Because I think a lot of people have great stories but they tell them in a rambling way. Lucas: Three elements. First, you need to establish the stakes and the time constraint — not just 'it was urgent' but what specifically was on the line. Second, you need to show your quick triage — how did you sort the information you had, what did you treat as must-know versus nice to know. And third, you need to show that you made a call and communicated it clearly. The outcome matters less than demonstrating that you had a deliberate method. Luna: I love that. And I'd add a fourth element that a lot of people miss: showing that you thought about the ripple effects. Like in that logistics story, the candidate considered the less senior employee's experience — that's not just about the immediate fix, that's about the longer-term impact. Lucas: That's a really good addition, because it shows you're not just a firefighter. You're thinking about morale, about training, about downstream consequences. And that's exactly the kind of judgment a hiring manager wants to see. Now, let's talk about the traps — because there are a couple of classic mistakes that turn a good story into a red flag. Luna: Okay, what's number one? I'm guessing it's making it sound like you didn't consult anyone. Lucas: Yes — that's a big one. Some candidates think admitting they asked for help makes them look weak. But in real life, most quick decisions happen in a ecosystem. The hiring manager I spoke to said she actually looks for whether the candidate knew when to escalate or loop someone in. If you claim you went it alone and it worked perfectly, that can sound either arrogant or like you didn't have real stakes. Luna: Right. And the flip side — the other trap is making it sound like you made the decision and then never checked back on it. A quick decision isn't a one-and-done. You need to show you followed up or adjusted. Lucas: Exactly. A candidate who says 'I made the call and it worked' is giving a static answer. A better answer shows a feedback loop — they made the call, then monitored the outcome, then tweaked. That's especially important in roles that involve project management or ops. So, how should someone actually structure their answer in the moment? Let's talk about the S-T-A-R method, but with a twist for this specific question. Luna: Sure, but I want to bring in a quick personal story here, if that's okay. When I was a hiring manager, I asked this question to a candidate for a marketing role. She told me about a time she had to pull a campaign asset together with a two-hour deadline because a vendor dropped the ball. But she didn't just talk about logistics. She talked about how she quickly assessed the target audience, repurposed an existing asset, and communicated the change to the stakeholders. It was a huge time crunch, but her answer was so calm and structured that I remember it years later. Lucas: That's a perfect example — and it shows that the question isn't only for ops or logistics roles. It applies across functions. The interviewer is looking for the same thing: can you prioritize, can you communicate under pressure, can you think on your feet. Now, one thing I want to dig into is the follow-up questions. Because interviewers often don't just stop at the first story. They'll ask things like 'what would you have done differently?' or 'how did you know you had enough information?' Luna: Oh, that's a great point. How do you handle those without getting flustered? Lucas: The key is to treat the follow-up as part of the same story. If they ask 'what would you have done differently,' don't scramble for a new example. Just say 'looking back, I might have escalated earlier' or 'I would have checked with the customer before rerouting.' It shows self-awareness. And if they ask 'how did you know you had enough information?' — that's your chance to show your judgment criteria. You can say something like 'I knew I had enough when I had the critical path figured out, and I could always adjust the rest later.' Luna: That's a nice way to frame it. I also think it's smart to have two stories ready — one for a time when you made a decision that worked out, and one for a time when you made a decision that didn't go perfectly. Because interviewers sometimes want to see how you handle failure within a quick decision. Lucas: Absolutely. And that ties into something I want to mention — this is actually a good moment to talk about how we keep this show going. You know, we put a lot of research into breaking down these questions and giving you frameworks you can actually use. If today's episode helped you think through how you'd answer this question, or if you've ever used one of our tips to land a role, that's the kind of thing that keeps us motivated. And if you want to support us, you can buy us a coffee at buy me a coffee dot com slash fexingo. It's a small gesture, but it genuinely helps us keep this podcast ad-free and focused on the content. Luna: Yeah, it's a nice way to say thanks if you've gotten value from the show. No pressure, but we appreciate every little bit. Lucas: Alright, so back to the question. Let's talk about how to prepare your own story. The first step is to identify a moment where you had to make a decision with limited time and information. It doesn't have to be a huge crisis. It can be something like deciding whether to push back a deadline or choosing which task to tackle first when everything is urgent. Luna: And you should practice telling it out loud. It sounds silly, but it makes a huge difference. I've seen candidates who have a great story but they tell it in a rambling way, and the interviewer loses the thread. Lucas: Totally. And when you practice, focus on the verbs — 'I assessed', 'I prioritized', 'I communicated'. That keeps the story action-oriented. Also, be mindful of how long you talk. The full story should be around ninety seconds max. If it takes longer, you're probably not being concise enough. Luna: That's a good rule of thumb. And I'd add that you should end with a quick takeaway — what did this experience teach you about decision-making? That wraps it up nicely and leaves a lasting impression. Lucas: Perfect. So to recap for our listeners: when you get the 'quick decision' question, remember three things. One, show your process, not just the outcome. Two, demonstrate that you considered the ripple effects. And three, be ready for follow-ups that probe your judgment. If you can do those, you'll turn a tricky behavioral question into a chance to shine. Luna: And if you want more practice, we've got a whole library of interview prep episodes — you can find them on our website. Lucas: That's right. And if you have a question you'd like us to cover, send it in. We love hearing from listeners. Until next time, keep preparing, and you'll be ready for anything they throw at you.