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: Let's say you send a report to your boss on Tuesday. They forward it to their boss on Wednesday with a few tweaks. On Thursday, the VP finds a glaring error. And on Friday, your boss calls you in and says, 'This mistake is on you. I trusted you to get it right.' Luna: Oof. That's a gut punch. Especially when you know the error was introduced by their changes. Lucas: Exactly. That's today's topic — a boss who blames you for their own mistakes. It's one of the most corrosive dynamics in a workplace, because it's not just unfair. It erodes your reputation with people above your boss, people whose trust you may never get back. Luna: Yeah, and I think a lot of listeners have been there. So let's start with a real case to ground this. Lucas: Sure. I talked to a product analyst at a mid-size SaaS company — let's call her Priya. Her director, Raj, had a habit of rewriting her data summaries before sending them to the VP. He'd change a key assumption or rephrase a conclusion. Then when the VP questioned it, Raj would say, 'Priya's analysis had some issues. I tried to clean it up, but the core data was flawed.' Luna: So he framed himself as the fixer and her as the source of the problem. Classic blame-shifting. Lucas: Right. And the VP never saw the original version. Priya's direct manager was the gatekeeper of all upward communication. So her only option was to either accept the blame or figure out a way to make the truth visible without looking like she was throwing Raj under the bus. Luna: That's a narrow path. How did she handle it? Lucas: She did something smart. She started a shared document — a weekly data summary — that Raj could comment on, but the edit history was visible. She also began sending a brief email after their one-on-ones: 'Just to confirm, I'll update the Q3 forecast based on your feedback about the churn assumption.' Nothing accusatory. Just a paper trail. Luna: She built an evidence chain without ever saying 'You're wrong.' I like that. Did it work? Lucas: It took about two months. The VP eventually noticed the email thread and asked Raj directly about a specific change. Raj couldn't blame Priya because the email timestamp showed he'd asked for the change. So the blame shifted back to him, but not because Priya pointed a finger — because the facts surfaced naturally. Luna: And that's the gold standard, right? You want the truth to emerge without you having to play the role of accuser. Lucas: If today's episode helps you think through a situation like Priya's — or if you've ever been blamed for something that wasn't your fault — here's the thing. The reason we can do deep dives on these specific cases without ads is listener support. So if this felt useful, you can help keep it going at buy me a coffee dot com slash fexingo. That's a small way to say 'this matters' and it means we never have to sell your attention to a sponsor. And honestly, that keeps these conversations honest. Luna: Yeah, it's a direct line. No middleman. Every listener who chips in is basically saying 'keep digging into the real stuff.' We appreciate it a lot. Lucas: So back to Priya. Her approach worked because she didn't try to confront Raj directly. She just created a system where the truth couldn't be hidden. That's the first principle when you're dealing with a boss who blames you: document without accusation. Luna: Right. The moment you sound defensive or accusatory, you become the problem in their eyes. So how do you document in a way that feels neutral? Lucas: Use 'we' language. Instead of 'You changed the numbers,' say 'I want to make sure we're aligned on the version. Could we use the one from Tuesday?' Or send a recap: 'Per our conversation, I'll incorporate the updated revenue figures you provided.' That way, if someone downstream questions the numbers, it's clear where they came from. Luna: And if the boss is the type to deny they ever asked for the change, you've got the receipt. Lucas: Exactly. But there's a second principle, which is harder: don't get drawn into a blame game in real time. If your boss says 'This error is your fault,' your instinct is to say 'No it's not.' That's a fight you will lose, because they have positional authority. Instead, acknowledge the error and pivot to solution: 'I see the mistake. Let me trace back to understand how it happened and make sure it doesn't recur.' That buys you time to gather evidence. Luna: That's really good. You're not admitting fault — you're just saying 'let me investigate.' And in the investigation, the truth comes out. Lucas: Right. But I want to be honest — this strategy works best when the blame is occasional and the boss is somewhat rational. If you have a boss who systematically scapegoats you, every single time, documentation might protect you from being fired, but it won't fix the relationship. Luna: So when do you escalate? I mean, there comes a point where you need to talk to someone above them or to HR. Lucas: That's the third principle: know the difference between a bad boss and a toxic one. A bad boss might blame you in a moment of stress, then later apologize or course-correct. A toxic boss uses blame as a pattern — it's how they maintain control. If you see the pattern, you need to build a case before you escalate. Luna: And by 'build a case,' you mean a chronological record of incidents, with dates and evidence. Lucas: Yes. Priya kept a simple spreadsheet: date, project, what happened, what evidence she had. She never used it against Raj directly. But when she eventually interviewed for an internal transfer, she could honestly say she'd delivered solid work — and the VP, who'd seen the emails, backed her up. Luna: So the documentation served a dual purpose: it protected her in the moment, and it helped her reputation long-term. That's smart career management. Lucas: Exactly. But let's talk about the worst-case scenario: what if you escalate to HR and nothing happens? I've seen that a lot. Luna: Yeah, HR is not a magic fix. They're there to protect the company, not you. If your boss is a high performer, they might get a slap on the wrist. Lucas: Right. So before you escalate, ask yourself: what outcome do I want? If you want the boss to change, HR probably can't deliver that. If you want to transfer teams, HR can sometimes facilitate that — especially if you have a record of good performance and a paper trail. If you want to leave, then the documentation becomes leverage for a clean exit or a severance negotiation. Luna: That's a sobering lens. But I think it's realistic. The best outcome for Priya wasn't that Raj got fired — it was that she got a better role on a different team, and the VP started questioning Raj's data more carefully. Lucas: Exactly. She didn't win a battle; she won a campaign. And that's often the move — not to defeat the boss, but to make yourself bulletproof and then create options. Luna: So let's recap the framework. First, document without accusation — use 'we' language and email recaps. Second, don't get drawn into real-time blame; pivot to investigation. Third, build a case before escalating, and know what outcome you're aiming for. Lucas: And one more thing: take care of your own headspace. Being blamed for something you didn't do is emotionally draining. You start to doubt yourself. Priya told me she spent weeks second-guessing every number. So find a peer or a mentor outside your reporting line who can reality-check you. Luna: External validation is huge. Because when your boss is telling you you're the problem, you need someone else to say 'That doesn't add up.' Lucas: Yeah. And if you don't have that person internally, consider a professional coach or even a therapist. This stuff takes a toll. Luna: So final question: is there ever a scenario where you confront the boss directly and say 'You blamed me for something you did'? Lucas: Rarely, and only if you have a relationship where that conversation is possible. I've seen it work exactly once — when a director and his VP had a long-standing trust, and the VP admitted he'd been unfair. But that's the exception. For most people, direct confrontation just gives the boss more ammunition. Luna: So the play is: protect yourself, build options, and move on when you can. Lucas: That's the play. And if you're in that situation right now, I know it feels personal. But it's not about you — it's about a leader who lacks the spine to own their mistakes. Your job is to manage your career around that reality, not to fix them. Luna: Wise words. And if you've got a story about a boss who blamed you — or a strategy that worked — we'd love to hear it. You can reach us through the show page. Lucas: Yeah, we read every message. And until next time, keep your documentation clean and your reputation cleaner.