Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Takes Credit for Your Ideas in Private
Transcript
- Lucas: So there's this stat from the Workplace Bullying Institute — they surveyed about 1,500 US professionals last year, and 38 percent said their boss had taken credit for their work at least once. But here's the part that gets me: only 12 percent actually confronted the boss about it. Luna: That gap is huge. So most people just let it slide? Lucas: Right. And the typical advice you see online is 'speak up in the meeting' or 'send a follow-up email to the whole team.' But what if the theft happens in private? You pitch your boss an idea in a one-on-one, they nod, say 'that's interesting,' and then three days later they present it in the weekly all-hands meeting as if it was their brainchild. No mention of you. Luna: Ugh. I've had that happen. It feels like being invisible. You want to say something, but you also don't want to look petty or like you're not a team player. Lucas: Exactly. And that fear is real. The same survey found that people who did confront their boss reported higher levels of retaliation — things like being excluded from meetings, getting worse assignments, or even being fired. So the instinct to stay quiet is understandable. Luna: So what do you do when it's your word against theirs? You can't exactly say 'I told you that in private.' Lucas: You need to change the game before the theft happens. The first strategy is what I call the pre-meeting recap. After you pitch an idea in a one-on-one, send a short email right after — not accusatory, just summarizing. Something like: 'Thanks for the chat earlier. To make sure I'm on the right track, I'll move forward with the idea we discussed about X and Y.' Luna: So you're creating a paper trail before they can run with it. Lucas: Exactly. Now there's a timestamped record that you originated the idea. If the boss presents it as theirs later, you have documentation. But more importantly, most bosses will realize you've put it in writing, and they'll either credit you or avoid using the idea altogether because they can't claim it cleanly. Luna: I like that. But what if you forget to send the email, or the boss presents the idea the very next day? Lucas: Then you move to strategy two: the innocent clarification in a group setting. When the boss says 'I've been thinking about this new approach,' you don't say 'That was my idea!' — that's confrontational and will backfire. Instead, you say something like 'Oh, that's interesting — that sounds a lot like the approach we discussed in our one-on-one on Tuesday. Did you want me to take the lead on that?' Luna: That is smooth. You're not accusing, you're connecting. And you're offering to do the work, which makes you look proactive. Lucas: Right. And if the boss says 'No, this was my idea,' you can gently add 'Huh, we must have been thinking along the same lines. Great minds.' That keeps the relationship intact while planting a seed in everyone else's mind that you might have been involved. Luna: But what about bosses who are serial offenders? The kind who do this every week? Lucas: That's where strategy three comes in: the documentation as leverage approach. Keep a private log — date, time, idea shared, context. After three or four instances, you have a pattern. Then you can schedule a performance feedback conversation with your boss and say 'I've noticed a trend where ideas I've brought to you in our one-on-ones later appear in meetings without attribution. I want to make sure my contributions are recognized so I can continue to be motivated.' Luna: That frames it as a performance issue, not a personal attack. And it gives the boss a chance to correct without losing face. Lucas: Yes. And if the behavior continues after that conversation, you escalate — to your boss's boss or HR. But with documentation, you're not making a he said she said accusation. You have a log that shows a pattern. Luna: That's really practical. I think a lot of people worry that documenting feels paranoid, but it's actually just professional. Lucas: It is. And look, there's a psychological reason some bosses do this. It's often about insecurity — they feel their own position is shaky, so they take credit for their team's ideas to bolster their own standing. Understanding that doesn't excuse it, but it helps you not take it personally. Luna: Yeah, that reframe is helpful. It's not about your idea being bad — it's about their need to look good. Lucas: Exactly. And if you can find ways to make them look good while still getting credit — like saying 'I'm glad you liked my idea about X, and I think we could implement it by doing Y' — that can be a win-win. Luna: So it's about managing the relationship, not just the moment. Lucas: That's the core of managing up. And honestly, having these conversations is tough. It takes confidence and a bit of risk tolerance. But if you never speak up, the pattern continues. Luna: Totally. And speaking of taking action — if we've helped you think through a career move or a tricky conversation like this, and you've gotten value from these episodes, you can support the show at buy me a coffee dot com slash fexingo. It's a couple of dollars a month, and it genuinely helps us keep making these episodes ad-free. Lucas: Yeah, it's listeners like you who keep us going. Every small contribution makes a difference. Luna: Alright, back to the strategies. One more I want to add: when you share an idea in a one-on-one, you can proactively ask 'Would you like me to present this to the team at the next meeting?' That way, you're offering to be the public face, and it's harder for the boss to steal it later. Lucas: That's a great one. It forces the boss to either agree — which gives you the stage — or say no, which is awkward for them. Most will say yes to avoid looking like they're blocking you. Luna: And if they say no, you can follow up with 'Okay, I'll send you a summary so you can share it accurately.' That creates the paper trail we talked about. Lucas: Exactly. The key is to never leave a one-on-one without some form of documentation — an email, a shared doc, a calendar note. Because memory is fallible, and bosses who steal ideas often rely on that fuzziness. Luna: One thing I wonder: does this work with bosses who are genuinely malicious? Like, the ones who know exactly what they're doing? Lucas: It's harder. Malicious bosses will find ways around it. But documentation still protects you — it establishes a record that you can use if you need to escalate. And sometimes, just the act of documenting makes you feel more empowered, even if you never use it. Luna: That's a good note. It's not just about the outcome — it's about protecting your own sense of professionalism. Lucas: Right. And if the situation is truly toxic, the best strategy might be to get out. But in the meantime, these tactics can help you survive and even thrive. Luna: Absolutely. Let's wrap with a final tip: if you do get credit in a meeting, even if it's after the fact, make sure to acknowledge it gracefully. Say 'Thanks for mentioning my contribution.' That reinforces the behavior you want to see. Lucas: Yes. Positive reinforcement works on bosses too. When they get it right, let them know. They're human. Luna: Alright, that's a good place to leave it. Next episode, we're tackling 'How to Manage a Boss Who Changes the Rules Mid-Project' — one of your most requested topics. Lucas: Can't wait. See you next time.