Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Blames You for Their Mistakes
Transcript
- Lucas: You are in a quarterly review. Your boss is presenting your team's results, and you know the numbers are bad because they killed a campaign you told them not to kill. And then you hear them say, 'Well, the marketing team didn't execute on the revised strategy.' Luna: That specific feeling — where you know it's a lie and you can't call it out in the moment without looking defensive — that is one of the most isolating moments at work. Lucas: And it is surprisingly common. A 2024 survey from the Workplace Bullying Institute found that 29 percent of employees reported being blamed for something they didn't do. But the number jumps to over 40 percent when you filter for people who work for a boss they describe as difficult. Luna: So this isn't rare. Which means we should have a playbook for it. And I know we have covered other flavors of the difficult boss — credit-stealing, micromanaging, vague feedback — but blame-shifting is different because it's reactive. It happens in real time, often in front of other people. Lucas: Exactly. And the instinct is to defend yourself immediately. But that usually makes you look guilty or emotional. Today I want to walk through a specific case — a listener story that came in — and then talk about the three-step strategy that actually works. Luna: Let's hear it. Lucas: I'll change the name and some details, but the core is real. Sarah worked as a brand manager at a large consumer goods company. Her boss, let's call him Mark, approved a packaging redesign for a new product launch. Sarah flagged a risk — the supplier had a history of delays — but Mark said go ahead anyway. Luna: Classic setup. Lucas: The delay happened. The product missed the shelf date. During the post-mortem with the VP, Mark said, 'Sarah's team didn't vet the supplier properly. We need better due diligence.' Sarah said she sat there with her mouth open. She had an email chain proving she raised the risk, but she froze. Luna: And that freeze is totally understandable. You're in a meeting with senior leadership, you don't want to be the person pulling out evidence and making your boss look like a liar — even though they are. So what did Sarah do? Lucas: She did the natural thing: she stayed quiet in the meeting, then went to Mark's office afterward and said, 'I want to clarify what happened with the supplier.' Mark brushed it off. 'Look, it's over, let's move forward.' That's the classic blame-shifter's tactic — they want to control the narrative in the moment and then shut down any correction. Luna: So the immediate correction didn't work. What did she do next? Lucas: She came to me for advice. And the strategy I gave her had three parts. First, don't try to correct the narrative in the heat of a meeting — that's too late. Second, document the decision trail immediately, before the next meeting. Third, reframe the conversation from 'who is to blame' to 'what can we learn' — which allows you to surface the truth without accusing. Luna: The reframing is the part I think is most counterintuitive. Because your instinct is to say, 'Actually, Mark approved the supplier.' But that puts Mark on the defensive, and now you have a personal conflict on top of the professional one. Lucas: Right. So instead, Sarah scheduled a follow-up with the VP — not to complain about Mark, but to 'share some context on the supplier timeline so we can improve our process.' She framed it as a learning exercise. Then she shared the email chain where she flagged the risk and Mark overrode her. Luna: And how did that land? Lucas: The VP saw the full picture. Mark didn't get fired, but the VP started asking Mark directly for risk assessments in future meetings. Sarah said she felt like the air cleared. More importantly, she stopped being the scapegoat for everything that went wrong after that. Luna: But I want to add something here. This only works if you actually have the documentation. If you don't have the email or the meeting notes, it's much harder. And a lot of people don't document because they trust their boss — until they don't. Lucas: That's a really important point. And it's why the first step — documenting in real time — is actually the most critical. You have to create a paper trail before you need it. A brief email after every key decision: 'Just confirming we agreed to move forward with Supplier X despite the delivery risk I noted.' Then you have the record. Luna: And that email is not aggressive. It's just good project management. But it becomes your shield. Lucas: Yeah. And look, this whole topic — managing a boss who blames you — it's one of those things where a little bit of forethought saves you a lot of pain. And I think that's why episodes like this are worth making. Luna: I agree. And it's also why listener support matters. We don't run ads on this show, and that's intentional. It means we can talk about real cases without worrying about sponsors. A small group of listeners chips in monthly through buy me a coffee dot com slash fexingo, and that's literally what keeps us recording every week. Lucas: Honestly, that support made a difference when we were deciding whether to keep going after season one. So if this show has helped you navigate a tough work situation, it's a way to keep it ad-free and independent. Luna: Exactly. No pressure — just putting it out there. Now, back to blame-shifting. One thing I've seen work well is the 'pre-mortem' approach. Before a project launches, you and your boss agree on exactly where accountability lies for different risks. That way, if something goes wrong, the conversation is already framed. Lucas: That's smart. And it's especially useful if you've already been scapegoated once. You can say, 'To make sure we're aligned on accountability this time, can we document who owns each risk?' If your boss resists, that's a red flag. Luna: Right. And if they do resist, you might need to think about whether this is a pattern you can manage or a pattern you need to leave. Because chronic blame-shifting is often a sign of a deeper leadership failure. Lucas: Yeah. And that's the hard question. If it's a one-time thing, the reframing strategy works. If it's every quarter, you're dealing with someone who sees scapegoating as a management tool. And in that case, your best move might be to build a relationship with someone two levels up — not to tattle, but to make sure your reputation is known outside your boss's filter. Luna: Which is another reason to document everything. If you eventually need to transfer or leave, that paper trail helps you tell your story without sounding like you're complaining. You just show the decisions. Lucas: Exactly. So to wrap this up: if you're in that quarterly review and your boss blames you for something they decided, don't defend yourself in the moment. Nod, take notes, and later reframe the conversation as a process improvement. And always, always confirm decisions in writing — before you need to. Luna: And if you've got a story about a time you were blamed for something that wasn't your fault, we'd love to hear it. We might share it — anonymized — on a future episode. Lucas: That's it for this one. We'll be back later this week with another difficult boss scenario. Until then, keep your chin up and your email chain clean.