Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Takes Credit for Your Work
Transcript
- Lucas: You know that feeling when you're in a meeting and your boss presents your analysis, your numbers, your slide—and they don't mention your name once? It's like watching a magician perform a trick with your own props. Luna: Oh, I've been there. It's a special kind of slow burn. And it's actually one of the most common complaints I hear from listeners—the boss who systematically takes credit for your work. Lucas: Right. And it's tricky because sometimes it's negligent, sometimes it's strategic. But the outcome is the same: you do the work, they get the shine. So today we're going to get specific about what you can actually do about it. Luna: If this episode helps you navigate a situation you're in, the reason these conversations stay ad-free is listener support. People who find real value here can help keep it going at buy me a coffee dot com slash fexingo. And now, let's get into the playbook. Lucas: Exactly. So let's start with a real case. A listener—let's call her Maya—worked as a mid-level marketing manager at a large retail chain. She noticed her boss would regularly forward her weekly reports to the VP with just a one-line note: 'Key findings attached.' No attribution. Luna: That's the classic 'Insecure Inheritor' move. They're not malicious necessarily—they just assume that because it came from their team, it's theirs to present. Lucas: Right. And Maya's first instinct was to talk to her boss directly. She said, 'Hey, I'd appreciate if you could mention my name when you share my work.' And her boss said, 'Oh, of course, sorry.' And then nothing changed. Luna: That's the frustrating part. Often the verbal conversation doesn't stick because there's no consequence. So what did Maya do next? Lucas: She started a simple documentation practice. Every time she sent a report, she'd BCC her personal email. And she also started sending a brief summary email to her boss after every meeting where her work was discussed—just a quick, 'As discussed, here's a recap of the data I shared, which informed the decisions.' She was creating a paper trail. Luna: But that's still internal to their channel. Doesn't the boss just delete it? Lucas: In Maya's case, the breakthrough came when her boss presented her analysis at a quarterly review to the VP. Maya had the original timestamped email with the data attached. She forwarded that email to the VP with a note: 'Glad my analysis was useful in the review. For context, I prepared this on March 12th, attached here.' She didn't accuse anyone—she just added information. Luna: And that's the key. You're not attacking the boss, you're just completing the record. In a corporate environment, that's hard to argue with. Lucas: The VP actually replied thanking Maya for the additional context and started CC'ing her directly on related decisions. So the boss couldn't filter her out anymore. Luna: That's a smart structural fix. But what about situations where the boss is more actively erasing you? Like the 'Strategic Eraser' who deliberately omits your name to make themselves look indispensable? Lucas: That's a different beast. With the Strategic Eraser, the pattern is intentional. They might say things like 'I've been working on this' when it's clearly your project. Or they reframe your idea in a meeting and everyone treats it as new. For that, you need a preemptive approach. Luna: What does that look like? Lucas: You claim your work in real time, publicly, but politely. In the meeting, when your boss paraphrases your idea, you say, 'Thanks for building on my earlier proposal—I think we're aligned.' You're not confrontational, but you're anchoring the origin. Do that consistently and people start seeing the pattern. Luna: There's also the 'Over-Editor'—the boss who asks you to draft something, then changes a word or two and presents it as theirs. That can be even harder to prove because they did technically contribute. Lucas: Right. And that's where you have to ask yourself: is this a pattern or a one-off? If it's occasional and they still credit you in other ways, it might be a quirk. But if it's systematic, you need to build visibility. One tactic is to start looping in a third party early in the process. Send a draft to your boss with a CC to a colleague: 'Here's the first pass on the quarterly analysis, happy to incorporate feedback.' Now there's a witness. Luna: I also think there's a bigger conversation about the culture of the organization. If credit theft is rewarded, then no individual fix will fully protect you. At some point, you have to assess whether this boss is a blocker to your growth. Lucas: Absolutely. And the data backs that up. A 2023 study from the Journal of Organizational Behavior found that employees who experienced chronic credit theft reported 40% lower job satisfaction and were 2.5 times more likely to start looking for a new job within six months. So it's not just an ego thing—it affects retention and performance. Luna: Forty percent lower satisfaction—that's huge. So the personal cost is real. But let's talk about the one thing someone can do tomorrow if they suspect this is happening. Lucas: Start a 'work journal'. Every day, write down what you did, who you shared it with, and any acknowledgment you received. Do it in a digital format with timestamps—Google Docs or a private Slack channel. It's not for HR, it's for you. After two weeks, you'll see patterns. And if you ever need to escalate, you have a timeline. Luna: And if you do escalate, what's the right framing? Lucas: Don't say 'My boss is stealing my credit.' Say 'I want to ensure my contributions are visible to the leadership team so I can grow in my role.' That's harder to dismiss. Frame it as a development need, not an accusation. Luna: That's smart. And it works because you're asking for something reasonable—visibility—not punishment for your boss. Lucas: Right. And if nothing changes after that? Then you have a decision to make. Maya ended up leaving for a competitor where her new manager actually introduced her to the team as 'the person who does the analysis.' She said it felt like breathing fresh air. Luna: Sometimes the best career move is to find a boss who sees you. But the documentation and the public anchoring can buy you time and leverage while you figure that out. Lucas: Exactly. So to recap: three types—Insecure Inheritor, Strategic Eraser, Over-Editor. For each, a calibrated response. And the common thread is: make your work traceable, claim it politely in public, and frame any escalation as a growth request. It's not about winning a fight—it's about making sure your contribution can't be ignored. Luna: And if you've dealt with a credit thief before, we'd love to hear what worked for you. Sometimes the best strategies come from listeners who've been through it. Lucas: Absolutely. That's it for today. Thanks for being here—we'll talk again soon.