Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Describe a Time You Had to Make a Quick Decision Question
Transcript
- Lucas: Luna, I want to tackle a question that I think catches more candidates off guard than almost any other behavioral question, and it's not really about failure or conflict or leadership — it's about speed. Luna: Tell me about a time you had to make a quick decision. That one? Lucas: Exactly. On the surface it sounds easy — everyone's made quick decisions — but the trap is that if you tell a story that sounds rushed or reckless, you look like you lack judgment. And if you tell a story where you spent too long deliberating, you didn't answer the question. Luna: It's a tightrope. I've seen candidates freeze because they want to sound thoughtful, but the whole premise is that you had to act fast. Lucas: Right. So let's use a real example. I was talking to a product manager at a fintech startup — let's call her Priya — who got this question in an interview for a senior PM role at a payments company. She told me her story, and I think it's a great model because it has a clear constraint, a clear decision, and a clear outcome. Luna: What was the situation? Lucas: She was leading the launch of a new peer to peer payment feature. The marketing team had already announced a release date to a group of beta users. Then, two days before launch, her engineering lead discovered a bug that could cause a transaction to fail in a specific edge case — maybe one in every five hundred transactions. It wasn't a security issue, just a reliability gap. Luna: So she had to decide: delay the launch and lose the marketing momentum, or ship on time and risk some users hitting the error. Lucas: Exactly. And the interviewer wanted to know how she made that call. She had maybe two hours to decide because the engineering team needed to know whether to pull an all-nighter to fix it. Luna: What did she do? Lucas: She didn't just go with her gut. She collected three pieces of information fast. First, she asked the engineering lead how many users were likely to hit the bug in the first week — it was about fifteen out of eight thousand. Second, she asked customer support if they had capacity to handle maybe ten extra tickets. Third, she checked if the marketing team could still send an email warning beta users about a known issue. Luna: So she triaged the impact, not just the technical severity. Lucas: Exactly. She decided to launch on time, but with a proactive customer support note and a promise to fix the bug within seventy-two hours. The launch went well, only about a dozen users hit the error, and the fix shipped two days later. When she told that story in the interview, she framed it as: quick decision doesn't mean snap decision — it means gathering the minimum information needed to make a confident call. Luna: I love that. And I think that's the key to answering this question well. You want to show that you can move fast without being impulsive. Lucas: Right. And the structure helps. If you use a version of STAR — Situation, Task, Action, Result — you want to spend more time on the Action, specifically the mental process: what information did you gather, what trade-offs did you weigh, what was the timeline? Luna: And you want to be honest about the pressure. If you say 'I calmly weighed all options for thirty minutes' it sounds unrealistic. Better to say 'I had two hours, so I focused on the two factors that mattered most: user impact and fix timeline.' Lucas: Exactly. And here's a counterexample I've seen. A candidate once told me he had to decide whether to cancel a client meeting because his co-presenter got sick. He said he 'quickly reviewed the agenda and decided to go ahead.' That's too thin. I didn't learn anything about his judgment. Luna: What was missing? Lucas: He didn't tell me what factors he considered. Did he check if the client would reschedule? Did he prepare backup slides? Did he call his co-presenter to see if they could dial in? The story had no texture. A good quick-decision story needs a moment where the listener thinks 'oh, I wouldn't have thought of that.' Luna: So it's about demonstrating pattern recognition. You're showing that you've seen this type of situation before and you know which levers to pull. Lucas: Exactly. And if you haven't had a high-stakes quick decision in your career, you can use a smaller one. The scale doesn't matter as much as the structure. A chef deciding whether to substitute an ingredient when a supplier is late — same logic. Luna: That's a great point. One thing I'd add: sometimes the right quick decision is to ask for more time. If the question is about making a quick decision, it doesn't have to be a decision to act — it could be a decision to pause and escalate. Lucas: That's a really smart nuance. I once coached a candidate who worked in compliance. She got this question and told a story about a regulatory filing deadline. Her team realized they were missing a signature. She had to decide whether to file without it or ask for an extension. She chose to call her boss and the legal team, got a verbal confirmation, filed on time, and followed up with the signature later. That's a quick decision that shows judgment — she knew when not to go it alone. Luna: Right. And that's actually more impressive in some ways, because it shows you understand your own limits. Lucas: Yeah. So to wrap up the framework: when you get this question, pick a story where you had a clear time constraint, mention what information you gathered, explain your reasoning, and then show the outcome — even if the outcome was imperfect, as long as you learned something. Luna: And if the outcome wasn't perfect, own it. One candidate I know told a story where he decided to launch a feature with a known bug, and the bug caused a customer outage. He framed it as a lesson in when not to compromise on quality. That honesty actually made him more credible. Lucas: Exactly. Interviewers aren't looking for perfect records. They're looking for self-awareness and the ability to make a call under uncertainty. Luna: Speaking of things that are useful under uncertainty — if today's episode helped you think about your own quick-decision story, this podcast stays ad-free because of listener support. You can find us at buy me a coffee dot com slash fexingo. Just a small way to keep these deep dives coming. Lucas: Yeah, that really does make a difference for us. And it means we can keep doing episodes like this one — specific frameworks, real examples, no filler. Luna: Alright, back to it. One last tip: practice your quick-decision story out loud with a timer. If it takes more than ninety seconds, trim it. The question itself is about speed — your answer should reflect that. Lucas: That's a great litmus test. If you can't tell the story in under two minutes, you probably haven't distilled the decision clearly enough. Luna: And don't forget to name the trade-off explicitly. The most impressive part of Priya's story was that she weighed user impact against marketing momentum. That's the kind of specific trade-off that sticks in an interviewer's mind. Lucas: Yeah. So to summarize the key ingredients: a time constraint, a clear set of options, a rationale that shows pattern recognition, and a specific outcome. Avoid vague words like 'quickly decided' without explaining your logic. Luna: And one more thing — if you're in a virtual interview, don't rush. Quick decision doesn't mean fast talking. Take a breath, structure your answer, and deliver it with confidence. Lucas: Good point. Alright, that's the quick-decision question. Next time we'll talk about the 'tell me about a time you had to influence without authority' question — which is a whole other beast. Luna: Can't wait. For now, go practice your story. Good luck out there.