Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Survive a Boss Who Blames You for Their Mistakes
Transcript
- Lucas: You walk into a meeting you thought was going fine. Your boss opens with a sigh and says, 'Well, the client is unhappy with the timeline, and frankly, I was surprised to see the deliverable go out without my final sign-off.' Except you emailed them for sign-off three times, and they never replied. Luna: That moment when you realise they're about to use you as a human shield. I've been there. Lucas: Most of us have. And today we're talking about one of the most corrosive dynamics in any workplace: the boss who blames you for their own mistakes. Not just occasionally, but as a pattern. Luna: We're calling it the scapegoat boss. And Lucas, you found a really specific case that illustrates how to fight back without getting fired. Lucas: Right. There's a story from a project manager at a large retailer — I won't name the company, but think of a big-box chain you know. Over eight weeks, she tracked every instance where her director blamed her for something the director herself had dropped the ball on. Luna: Eight weeks. That's serious documentation. Did she go straight to HR? Lucas: No, and that's the first lesson. She did something smarter first. She identified the pattern and realised the director was under immense pressure from above — the VP was breathing down her neck about quarterly numbers. The blame-shifting was a symptom of insecurity, not just malice. Luna: So she didn't assume bad intent right away. That's actually generous, but also strategic. Lucas: Exactly. Step one: depersonalise it. Ask yourself, 'Is this a bad person, or a person under bad pressure?' In her case, it was mostly the latter. So she tried something counterintuitive: offering her boss a face-saving exit. Luna: A face-saving exit — meaning, give the boss a way to correct the story without admitting fault. Lucas: Yes. In the next one-on-one, she said, 'I noticed the timeline on the Johnson account seemed tight. I want to make sure we're aligned on the review process. Would it help if I sent a daily checkpoint email summarising where things stand?' She framed it as a system fix, not a blame accusation. Luna: And the director agreed? That seems like it could backfire if the boss is truly toxic. Lucas: It did work — for about two weeks. Then the director blamed her again for a missed deadline that was actually caused by the director approving changes at 9 p.m. the night before. That's when she knew it wasn't just stress; it was a pattern. Luna: So what was step two? Lucas: She started documenting with precision. Not just dates and times, but specific emails, meeting notes, and witnesses. Every time the director blamed her publicly, she'd follow up with an email: 'Per our conversation, I'll investigate the delay on the Smith project and report back.' That put the ball back in the director's court. Luna: And it also created a paper trail that shows she's proactive, not defensive. Lucas: Right. She also looped in a trusted peer from another department who had witnessed several of these exchanges. That peer later became a reference when she applied for an internal transfer. Luna: So she built a coalition. That's key — you don't want to be the only one telling the story. Lucas: But here's where it gets really interesting. After two months of this, the director blamed her in a meeting with the VP present. The project manager didn't defend herself in the moment. She just said, 'I'll review my notes and get back to you with a full timeline.' Then she emailed the VP directly — cc'ing her boss — with a clear, neutral timeline showing every delay originated with the director. Luna: That's gutsy. She essentially called the bluff in writing. Lucas: And she did it without accusing anyone. She just wrote, 'Here's a chronological record of the project milestones and sign-offs. Let me know if I'm missing anything.' The VP saw the pattern immediately. Luna: Did the director retaliate? Lucas: She tried. She gave the project manager a negative performance review two weeks later. But by then, the project manager had already applied for a lateral transfer to a different division, and the VP had seen enough to support the move. Luna: So she escaped without a war. That's the ideal outcome. Lucas: And honestly, most people don't get that. But the principles apply even if you can't transfer. Luna: If today's episode gave you a useful way to think about your own situation — whether it's a scapegoating boss or just a tricky relationship — we hope it helps. These conversations stay ad-free because listeners like you support the show. If you'd like to help keep it that way, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, we really appreciate that. It makes a difference. Luna: So back to the scapegoat boss. What about people who can't transfer — what's their play? Lucas: Great question. If you're stuck, you need to shift from defense to preemption. That means documenting in real time, not after the fact. Use a shared project management tool or send a weekly status email that's also cc'd to your boss's boss. Luna: That's risky if your boss is paranoid about being bypassed. Lucas: It is. So you frame it as transparency: 'I want to make sure leadership sees our progress.' The key is to make the documentation part of your normal workflow, not a special investigation. Luna: And if the boss is truly malignant — not just insecure but vindictive — when do you go to HR? Lucas: You go when you have a pattern of evidence and at least one witness willing to speak up. HR rarely acts on a single he said she said. But if you show them six incidents over three months, with emails and a colleague who saw the last one, they have to act. Luna: Or at least they have to open a file. Which is better than nothing. Lucas: Exactly. And here's a tactical tip: when you talk to HR, don't say 'my boss blames me unfairly.' Say 'I've observed a pattern of accountability breakdowns that's affecting project outcomes.' Speak their language. Luna: That's smart. HR cares about process and risk, not feelings. Lucas: Right. And if you frame it as a business problem, they're more likely to investigate. The project manager we mentioned — she eventually landed in a department where the director was a known developer of talent. Her reputation actually improved because the VP had seen her composure under fire. Luna: So there's a silver lining. Being the calm, competent person in a blame storm can earn you respect from the people who matter. Lucas: That's the paradox. If you handle it with professionalism, you often come out stronger. But it's exhausting in the moment. Luna: What about the emotional toll? Any advice for staying sane while you're in the middle of it? Lucas: Talk to a trusted mentor outside your reporting line. Someone who can affirm that you're not crazy. The gaslighting effect is real — you start to doubt your own memory. Having an outside perspective helps. Luna: And keep a private journal. Not for HR, just for you. It helps you see the pattern. Lucas: Exactly. And know that the average tenure of a toxic boss in many organisations is about 18 months before they get promoted or moved. You might outlast them. Luna: That's darkly funny. But true. Lucas: So to sum up: depersonalise, document, build allies, and frame it as a process issue. And if the pattern is clear and HR won't act, polish your resume and start looking. No job is worth your mental health. Luna: And if you have a story about a scapegoat boss, we'd love to hear it. You can find us on the Fexingo network. Lucas: For now, thanks for listening. We'll be back next week with another difficult boss survival guide.