Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / Managing a Boss Who Overreacts to Small Mistakes
Transcript
- Lucas: So, it's Tuesday morning, you hit send on an email, and there's a typo in the subject line. Not a big deal, right? Unless your boss treats it like a data breach and calls an emergency meeting. Luna: Oh, that's a very specific kind of Tuesday. And I think a lot of listeners know that feeling. The stomach drop when you realize you have to tell them something went wrong, even if it's tiny. Lucas: Exactly. And the instinct is to just be transparent, get it out there, apologize. But with an overreacting boss, that instinct can actually backfire. Today we're looking at how to manage a boss who overreacts to small mistakes — and how to deliver bad news in a way that keeps them calm and focused on the fix. Luna: I love this. Because it's not about hiding mistakes, it's about controlling the narrative before their amygdala takes over. Lucas: Right. And the first thing to understand is why they overreact. It's rarely about the typo. It's about control, or fear of looking bad, or they've been burned before and now they see every mistake as a sign of a bigger failure coming. Luna: And that's the key — it's not about you, it's about their internal alarm system. Lucas: So let's talk about a concrete strategy. The classic advice is 'just tell them early and often.' But that only works if you frame it right. If you walk in and say 'We have a problem,' you've already triggered the alarm. Instead, you want to lead with the fix. Luna: So you're saying don't say 'we have a problem,' say 'here's what I noticed and here's what I've already done about it'? Lucas: Exactly. There's a three-step framework I like: first, state the issue in one sentence, no drama. Second, immediately offer the solution or the plan. Third, ask for their input, which gives them a sense of control back. Let me give you a real example from a call-center QA manager I know. Luna: Good, give me a story. I'm all ears. Lucas: So this manager, let's call her Priya, she had a boss who would flip out if any QA score dropped below ninety percent. One week, her team's average slipped to eighty-eight because of a new software rollout. Priya knew if she just sent the number in a weekly email, she'd get a furious call. So she scheduled a five-minute chat, and she opened with: 'I want to flag a dip in our QA score this week. The main cause is the new software, and I've already scheduled extra training for Thursday. I'd love your take on whether we should also pause the rollout for a day.' Luna: And her boss just... calmed down? Lucas: In that case, yeah. Because Priya didn't give him a problem to solve. She gave him a decision to make. He felt in control, and he actually appreciated that she'd thought it through. It turned into a productive conversation about the rollout, not a blame session. Luna: That's a great example. And it's a skill — you're managing their emotional response as much as the facts. Lucas: And that's worth pausing on, because this is a show that runs on listener support. If this kind of practical framework is useful to you, the way we keep these episodes ad-free is through listeners who chip in — you can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, and it genuinely helps us keep the lights on and the mics warm. And it means we can keep digging into these situations without any sponsor pressure. Lucas: So, back to the framework. That first step — the one-sentence issue — is harder than it sounds. You have to strip out the self-blame and the hedging. No 'I'm sorry to bother you, but...' Just 'The X is Y.' Luna: And no 'maybe it's not a big deal but...' because that invites them to decide it is. Lucas: Exactly. Then step two, the fix. You need to have at least a starting point, even if it's a hypothesis. 'I'm going to check the logs and get back to you by two.' That shows forward motion. Luna: What if the mistake is really not your fault? Like, someone else on the team screwed up and you have to break the news? Lucas: That's a tougher one. And the instinct is to say 'it wasn't me.' But that can make you look like you're deflecting. Better to own the team's outcome. Say 'We missed this on our end' — even if you personally didn't — because you're presenting a unified front. That actually builds trust with your boss over time. Luna: That's a smart move — it shows leadership, not just accountability. Lucas: And it prevents the boss from playing 'find the guilty party,' which is never productive. Now, the third step — asking for input. This is where you give them a choice. 'Would you prefer I do A or B?' That satisfies their need for control without inviting a full-scale review of everything you've ever done wrong. Luna: But what if your boss is the type who doesn't want options, they just want to rant? Do you just let them vent? Lucas: Sometimes, yeah. If you know the rant is coming, you can preempt it by saying 'I know this is frustrating, and I want to hear your thoughts.' But keep it time-boxed. You can say 'Let's spend ten minutes on this and then we'll decide on next steps.' That way you're not absorbing hours of fury. Luna: And it shows you're not running from the conversation, you're managing it. Lucas: Right. Another angle: sometimes the overreaction is about the surprise itself. If you can build a habit of regular check-ins where you flag risks before they become issues, you're training your boss to expect that you'll surface problems early. That reduces the shock factor. Luna: So it's not just about the one conversation, it's about setting a pattern. Lucas: Exactly. And here's a counterintuitive tip: with a reactive boss, sometimes you want to under-communicate the severity initially. Instead of saying 'This is a major issue,' say 'I noticed something small that I want to fix before it grows.' That way they don't inflate it themselves. Luna: But isn't that just sugar-coating? I feel like some bosses see through that and get more annoyed. Lucas: That's a fair point. The key is to be factual, not minimizing. You're not saying 'it's nothing,' you're saying 'here's what I see, and here's the scope.' If you call it a 'small thing' but it's actually a client-facing error, you've lost credibility. So you have to calibrate. Luna: Calibration. That's a good word for it. Lucas: There's also the emotional labor aspect. You're essentially doing a bit of emotional regulation for your boss, and that's exhausting over time. So you need strategies to protect your own energy. That might mean debriefing with a trusted colleague, or writing down what you're going to say before you say it. Luna: And maybe limiting how much you absorb. You're not their therapist. Lucas: No, you're not. And one thing that helps is to keep a record of your proactive communication. If your boss is the kind who later claims 'you never told me,' you want a paper trail. A quick email after the conversation: 'As we discussed, here's the issue and the plan.' That covers you. Luna: That's a classic move. It's not about being defensive, it's about clarity. Lucas: Now, let's talk about what happens when the overreaction happens anyway. You've done everything right, and they still blow up. What do you do in the moment? Luna: I'm picturing a boss slamming their hand on the desk. Do you just sit there? Lucas: You don't have to absorb it silently. You can use a technique called 'name the emotion.' Say 'I can see this is really frustrating for you.' That can actually de-escalate because it shows you're paying attention, not dismissing them. Then give them a beat to respond. Luna: And if they don't calm down? Lucas: Then you can politely excuse yourself and say 'Let's continue this when we've both had a moment to think.' That's not running away, it's setting a boundary. You're allowed to leave a conversation that's becoming unproductive. Luna: I like that. You're not escalating, you're just refusing to be a punching bag. Lucas: And that's a skill in itself. Over time, these techniques can actually change the dynamic. Some bosses, when they see you're not rattled, they start to trust you more. They realize you're not going to bring them every little thing — you'll bring them the important things with a plan. Luna: So maybe the overreacting boss is really just a trust issue in disguise. Lucas: I think that's a fair read. And the way you build that trust is by consistently showing up with solutions, not just problems. It's a slow process, but it can turn a stressful relationship into something manageable. Luna: Manageable, not perfect. That's a good note to end on. Lucas: Yeah. Because you can't change who your boss is, but you can change how you interact with them. And that's worth a lot.