Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / The Boss Who Takes Credit for Your Work and How to Stop It
Transcript
- Lucas: Alright, let's talk about one of the most frustrating dynamics in any workplace: the boss who takes credit for your work. Not the accidental 'oh I forgot to mention your name' kind — the deliberate, repeated pattern where your manager presents your ideas, your analysis, your late nights, as their own. Luna: And it's not just annoying — it can actually stall your career. I've seen people miss promotions because their boss's boss had no idea who actually did the work. Lucas: Exactly. And there's a case I want to walk through today that I think gives us a really concrete playbook. It involves a senior analyst named Priya at a mid-sized consulting firm — roughly three hundred people, based in Chicago. She was up for promotion to manager, and she was universally respected by her peers. But her manager, let's call him Derek, had a habit of taking her slides, her client recommendations, and presenting them in leadership reviews as his own thinking. Luna: Classic. And I bet no one above Derek ever questioned it because he was the one in the room. Lucas: Right. The promotion committee saw Derek's name attached to the wins. Priya's name was buried in the project files. So when promotion time came, the committee actually said, 'Derek's individual contribution has been exceptional this year.' Meanwhile Priya had done about seventy percent of the client-facing analytical work. She didn't get the bump. Luna: Ouch. So what did she do? I'm guessing 'confront Derek in a meeting' was not the winning move. Lucas: It was not. In fact, she tried that — she sent him a polite email saying she'd appreciate if he could mention her contributions in the next leadership review. And Derek smiled, said 'absolutely,' and then proceeded to do the exact same thing three weeks later. Luna: Which tells you he's not just careless — he's intentional. Or possibly a narcissist. Lucas: That's the working theory. So Priya shifted strategy. Instead of asking for credit, she started a process I call 'document and brief.' The idea is simple: before any major deliverable goes to leadership, you create a one-page summary that explicitly lists who did what. Not accusatory — just factual. 'Data collection and modeling: Priya. Client presentation deck: Priya. Strategic recommendations: Priya and Derek.' Luna: And did she send that to Derek? Or to his boss? Lucas: Both. But the key was timing. She sent the document to Derek first, with a note: 'Here's the summary for the Q3 review. Please let me know if I've misrepresented anyone's role.' That gave Derek a chance to object — which he couldn't, because it was accurate. Then she cc'd Derek and sent it to the VP of the practice group, saying 'Per our process, here's the contribution breakdown for the project.' Luna: So she made the credit transparent without having to say 'Derek is stealing my work.' Lucas: Exactly. And it worked. The VP started noticing that Priya's name kept appearing in the 'lead analyst' slot on every major project. The next promotion cycle, she got the manager title. Derek was still there, but he couldn't claim ownership of work that was already documented. Luna: I love that it's not a confrontation — it's a process. Because if you make it about process, the boss can't easily get defensive without looking like they're trying to hide something. Lucas: Right. And there's actually data on why this matters. A 2024 study in the Journal of Organizational Behavior tracked employees who reported frequent credit theft by their managers. They found that those employees were 2.3 times more likely to quit within six months — and among those who stayed, productivity dropped by 18 percent. Luna: Eighteen percent is huge. That's not just a morale hit — that's real dollars lost for the company. Lucas: Absolutely. And yet most organizations don't have any mechanism to detect or address it. It's this invisible tax on performance. Luna: So what about the person whose boss is more sophisticated? Like, what if Derek had started adding his own contributions to the document and taking credit that way? Lucas: That's a fair point. And the 'document and brief' strategy assumes your boss will at least go along with the factual record. If they're willing to lie outright, you need a different approach. In those cases, I'd recommend building a coalition of peers who can corroborate your contributions. When three people independently say 'Priya built that model,' it's much harder for one manager to override. Luna: And that's where the 'brief' part of 'document and brief' comes in, right? You're not just writing it down — you're making sure the right people see it. Lucas: Exactly. The documentation is step one. But step two is making sure at least one person above your boss — or at least outside your immediate chain — knows what you did. That could be a skip-level meeting, a cross-functional project, or even just a well-placed cc on a status update. You're not complaining, you're informing. Luna: I also think there's a psychological piece here. A lot of people — especially if they're early in their career — assume that good work will be recognized automatically. And this case proves that's not true. Lucas: It really does. The 'just work hard and they'll notice' myth is one of the most damaging ideas in career advice. Because in many organizations, visibility is as important as output. And when your manager is a credit thief, they're actively blocking your visibility. Luna: So the antidote is to engineer visibility for yourself — without making it look like you're grandstanding. That's a fine line. Lucas: That's the skill. And Priya's method is a good template because it's factual, it's professional, and it doesn't escalate. She wasn't accusing Derek of theft. She was just clarifying roles. And that made it very hard for anyone to push back. Luna: What if your company has a culture where even that feels risky? Like, if you're in a very hierarchical org where cc'ing your boss's boss is seen as insubordination? Lucas: That's a real concern. In those environments, I'd start with the paper trail alone — document everything in a personal file. Not to share, but to have when you need it. Then, quietly start looking for sponsors in other departments. A lateral move might be safer than trying to fix the relationship with a toxic boss. Luna: And sometimes the answer really is to leave. The study said 2.3 times more likely to quit — sometimes that's the rational response. Lucas: Absolutely. No one should feel obligated to fix a broken system alone. But if you're not ready to leave, or if the job is otherwise good, the 'document and brief' approach gives you a way to fight for your work without fighting your boss. Luna: That's a good place to leave it. So the takeaway: if your boss takes credit, don't confront — document and brief. Make your contributions visible through process, not protest. Lucas: Exactly. And remember: the goal isn't to punish the boss. It's to make sure the people who matter know what you did. If you do that consistently, the credit will follow.