Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / Managing a Boss Who Takes Credit for Your Work in Meetings
Transcript
- Lucas: Let me start with a number. The Society for Human Resource Management published a study in 2023 — sixty-two percent of employees said their boss or a colleague had taken credit for their work at some point. Luna: Sixty-two percent — that's almost two out of three people. Lucas: Right. And it's one thing when it happens in a private email chain. It's another when it happens in a meeting, live, in front of your peers or senior leadership. That moment when your boss says, 'I had an idea,' and it's your idea. You're sitting there, and you feel a flash of heat. Luna: And you have maybe three seconds to decide what to do. Do you speak up? Do you let it slide? How do you not look like you're just turf-protecting? Lucas: Exactly. The instinct is to either freeze or blurt out 'That was my idea' — which can come across as defensive, even if you're right. So instead, I want to talk about a technique called 're-voicing with attribution.' Luna: Re-voicing with attribution — say more. Lucas: It's a phrase borrowed from mediation and facilitation. The idea is that you restate the point your boss just made, but you subtly tie it back to a previous conversation. For example, after your boss presents your idea, you say something like, 'That's a great way to build on the concept we discussed last Thursday in the one-on-one.' Luna: So you're not contradicting them. You're just adding context that reminds everyone where the idea originated. Lucas: Exactly. It's collaborative, not confrontational. You're not saying 'You stole my idea.' You're saying 'We developed this together.' And if your boss is smart, they'll pick up on that and maybe even hand the credit back gracefully. Luna: But what if the boss is not smart? Or what if they do it repeatedly, week after week? Lucas: That's when you need to move from in-the-moment tactics to a more systematic approach. I spoke to a product manager at a mid-stage SaaS company — let's call him Dan — whose boss was notorious for this. Dan started sending a brief email after every brainstorming session that summarized the ideas, with bullet points and who contributed what. He'd CC his boss and say, 'Just capturing our notes from today — feel free to add anything I missed.' Luna: Building a paper trail without making it look like you're building a paper trail. Lucas: Exactly. And the beauty is, if the boss later presents those ideas as their own, Dan has a dated document that shows the ideas were his. The boss might still take credit in a meeting, but Dan has ammunition if he ever needs to escalate. Luna: Escalation is a big step. When is it actually worth going to HR or skipping the boss? Lucas: I'd say two conditions need to be met. First, the behavior has to be pattern — not a one-off slip. Second, it has to have a material impact on your career. If your boss is taking credit for the idea that leads to a promotion or a bonus for them, and you're passed over, that's a problem. In that case, you want to have that paper trail ready when you talk to HR. Luna: And what do you say to HR? You don't want to sound like you're just complaining. Lucas: You frame it as a concern about team dynamics and fair recognition. You say, 'I've noticed a pattern where my contributions haven't been accurately attributed in meetings, and I'm worried it's affecting morale — and my ability to do my best work.' You're not accusing; you're raising a systemic issue. Luna: I read a case study from a tech startup where an entire engineering team adopted a protocol: after any meeting where ideas were shared, someone would post a summary in a Slack channel with 'credit lines' — like 'Feature X: Sarah's idea, UI tweaks: Marco.' They said it reduced credit theft by forty percent in one quarter. Lucas: That's brilliant. It normalizes attribution. It's not about one person fighting for credit; it's a team norm. If your boss isn't part of that channel, you can still do it for your own work. I've done it: after a meeting where my boss restated my idea, I'd send a follow-up email to the attendees saying, 'Great discussion today. I'm excited to move forward on the customer retention idea we landed on — looking forward to the next steps.' Luna: So you're claiming ownership in a way that's forward-looking, not backward-looking. Lucas: Right. You're not fighting over who said what first. You're positioning yourself as the person driving the idea forward. That's more powerful. And it also makes it harder for the boss to shut you out of the implementation. Luna: What about the psychological toll? I think people underestimate how draining it is to have your ideas repeatedly taken. Lucas: It's real. There's research on 'idea theft trauma' — it reduces your willingness to contribute. You start holding back in meetings, which hurts your performance and your reputation. That's why you have to address it, not just for the credit but for your own engagement. Luna: And if you hold back, the boss might then say you're not contributing enough. You can't win. Lucas: Which is why I advocate for a two-pronged approach: the in-the-moment re-voicing for the small stuff, and the systematic documentation and stakeholder alignment for the big stuff. And also — this is important — you need to build relationships with the other stakeholders in the room. If you have a good relationship with the VP who's in that meeting, you can follow up with them directly: 'Hey, I was really excited to hear my idea get traction. Let me know if you want to dive deeper.' Luna: That's a great way to bypass the boss as the sole gatekeeper of your visibility. Lucas: Exactly. And most bosses who do this aren't necessarily malicious. Some are just insecure. They feel like their job is to have the ideas, and they don't realize how damaging it is. Others are more Machiavellian. But regardless of motive, the effect on you is the same. So you have to protect your reputation. Luna: We should note that this is not about being petty. It's about career survival in some cases. Lucas: Absolutely. And it's also about fairness. The workplace functions better when ideas are properly attributed. It encourages more ideas. So when you advocate for yourself, you're actually helping the whole team. Luna: You know, speaking of helping the team — I think a lot of listeners come to this show because they're dealing with these exact dynamics. And we try to keep the show ad-free because we think that's the right thing to do. If you've ever found a piece of advice here useful, and you want to support that approach, you can find us at buy me a coffee dot com slash fexingo. No pressure, just if it's helped you. Lucas: Yeah, we hear from listeners all the time that the practical, no-hype style is what keeps them coming back. And it's the listener support that lets us keep it that way. So thanks for that. Luna: Alright, back to the topic. So one more tactic I want to mention: sometimes you need to have a direct conversation with your boss. Is there a script for that? Lucas: There is. You schedule a one-on-one, and you say something like, 'I've noticed that in recent meetings, some of the ideas I've shared have been presented without a clear attribution. I want to make sure our collaboration is visible to the rest of the team. How can we improve that?' You're framing it as a 'we' problem. Luna: And if the boss gets defensive? Lucas: Then you have your answer about their character. And you start that systematic documentation, relationship-building, and possibly looking for a new role. Because a boss who can't handle that feedback is unlikely to change. Luna: To wrap up, I think the key takeaway is: don't just fume silently. Have a strategy. Use re-voicing, build your paper trail, and build alliances. Lucas: And remember, the goal isn't to get revenge or to prove you're smarter. The goal is to get your work recognized so you can advance. Keep your eye on that prize.