Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer Tell Me About a Time You Had to Make a Tough Decision
Transcript
- Lucas: So, there's a question that comes up in almost every interview cycle for mid-to-senior roles: 'Tell me about a time you had to make a tough decision.' And the reason it keeps showing up is it's a proxy for how you handle trade-offs under pressure. Luna: Right. It's not just about the decision itself — it's about your process. Did you gather the right inputs? Did you involve the right people? How did you handle the fallout? Lucas: Exactly. And what trips most candidates up is they pick a decision that's too easy — like choosing between two vendors — or too personal, like deciding to leave a job. The interviewer wants work-relevant, objective, with real stakes. Luna: So what's a good example? Give me a specific case. Lucas: Let's use Stitch Fix — the personal styling service. A few years back, their product team had a classic trade-off. They were building out the 'Shop Your Look' feature, which lets clients browse items their stylist picked but also see more options. The product manager had to decide between two paths: Path A was a recommendation engine that used past purchase data to suggest new items — high engagement potential, but risky if the algorithm got it wrong. Path B was a simpler browsing interface that let clients filter by category — lower risk, lower potential upside. Luna: Tough call. And I'm guessing both had strong advocates. Lucas: Exactly. The engineering team pushed for Path A because it was technically interesting. The stylist team wanted Path B because they worried the algorithm would override their personal picks — which is a real trust issue. The PM had to decide. Luna: How did they frame the decision? Lucas: They used what I call the 'C4 framework' — Clarify, Consider, Commit, Communicate. First, they clarified the criteria: what mattered most? Client trust? Revenue? Speed to market? They ranked them. Then they considered the trade-offs using data — they ran a small A/B test on a subset of users. The test showed Path A increased click-through rate by 22% but decreased stylist satisfaction scores by 8 points. Path B had no negative impact on stylist satisfaction but only a 5% lift in click-through. So the decision came down to values. Luna: And Stitch Fix's core value is 'trust the stylist.' So Path B aligns better, even if it's less flashy. Lucas: Bingo. So the PM committed to Path B, but with a twist: they promised to revisit the recommendation engine in six months with better safeguards. Then they communicated the decision to both teams transparently — explaining the data, the values alignment, and the follow-up plan. That last part is huge — it shows you're not just making a call, you're managing the organizational impact. Luna: So when a candidate tells that story in an interview, they should hit those four Cs. But also — what about the 'tough' part? The emotional weight? Lucas: Good point. The best answers include a moment of tension. Maybe the PM initially leaned toward Path A because the data was compelling, but they changed their mind after talking to a frustrated stylist. That shows listening and flexibility, not weakness. Luna: Right. And avoid saying 'I knew I was right all along.' That sounds arrogant. Better to say 'I wrestled with it, and here's what tipped the scale.' Lucas: Yeah. And one more thing — if you're asked this question, don't pick a decision that was easy or obvious. Pick something with real ambiguity. For example, deciding to kill a project that your boss championed, or choosing between two team members for a promotion. Those have interpersonal stakes. Luna: Let's talk about a common pitfall: the candidate who tells a story where the decision was made by someone else. Like 'my manager decided we should go with option A, and I supported it.' That's not a tough decision you made. Lucas: No, that's a compliance story. You want ownership. So if you were a junior person, you could still frame a decision you influenced — like 'I had to decide whether to escalate a bug or fix it quietly before launch.' That's a real trade-off between transparency and speed. Luna: And for more senior roles, the stakes are bigger — like deciding to cut a product line or restructure a team. Those decisions affect people's jobs, so you need to show empathy and strategic thinking. Lucas: Right. And a quick structural tip: use the STAR method — Situation, Task, Action, Result — but for tough decisions, emphasize the 'Action' part by breaking down your thought process. Interviewers love hearing 'I considered three options and eliminated one because...' Luna: Let me ask you: what if the decision didn't work out? Can you still use it? Lucas: Absolutely. Some of the best answers are about decisions that failed but taught you something. The key is to show you took responsibility and learned. For example, a PM I know decided to launch a feature without enough user testing — it flopped. In an interview, they said 'I made a call based on speed, but I should have pushed for more testing. Now I always build in a validation phase.' That's honest and growth-oriented. Luna: That's actually more impressive than a success story sometimes. It shows self-awareness. Lucas: Exactly. And it's rare — most people are afraid to admit failure in an interview. But if you frame it right, it's a strength. Luna: Okay, so we've covered the framework, the example, the pitfalls. Let's talk about how to practice. Lucas, what's your number one tip for someone prepping this question? Lucas: Write out three different answers — one about a product decision, one about a people decision, and one about a process decision. Then practice saying them out loud until they feel natural. Record yourself and listen for filler words like 'um' or 'like.' And time yourself — aim for 90 seconds to two minutes max. Luna: That's solid. And I'd add: get feedback from a friend or mentor. They can tell you if your story actually shows decision-making or if it sounds like you were just following orders. Lucas: Good call. And if you're looking for more frameworks, the C4 one is in the show notes, but you can also use the 'OODA loop' — Observe, Orient, Decide, Act — which comes from military strategy but works great for business decisions. Luna: That's a good one. So to summarize: pick a real tough decision, structure it with C4 or STAR, show your thought process, admit if it didn't work, and practice your delivery. Lucas: Yeah. And one last thing — if we've helped you think through a career move or interview prep, a couple of dollars a month is genuinely what keeps these shows ad-free and independent. You can support us at buy me a coffee dot com slash fexingo. It makes a real difference — even just a few coffees a month keeps the lights on. Luna: Totally. And it's because of listeners like you that we can keep doing deep dives like this without sponsors. So thank you. Lucas: Alright, let's wrap with a final thought. Next time you're asked 'Tell me about a time you made a tough decision,' remember: the interviewer doesn't care about the decision itself as much as they care about your judgment. Show them how you think, and you'll stand out. Luna: And if you have a tough decision coming up in your career, good luck — you've got this. Lucas: Thanks for listening. This is Interview Prep with Fexingo.