Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Steals Your Ideas
Transcript
- Lucas: So you're in a meeting. You pitch an idea. The room goes quiet for a second — then your boss says, 'You know, I was thinking about that exact thing last night,' and proceeds to lay out your plan as if it's theirs. Luna: Oh, that moment. That specific moment where you feel your blood pressure spike and you're trying to decide if you should say something, and you almost always don't. Lucas: Right. And the worst part is, if you do speak up, you risk looking petty or insubordinate. But if you stay quiet, you've just let your idea get stolen in real time. It's a no-win — unless you have a strategy. Luna: I've been there. I had a boss once who literally took a slide I made, changed the font, and presented it to the VP as 'her framework.' I didn't say a word. I was too shocked. Lucas: And that's the default response for most people — freeze. But the research suggests this is more common than we think. A 2025 study from Harvard Business Review surveyed 1,200 knowledge workers and found that 43 percent had experienced idea theft by a direct supervisor in the past year. Luna: Forty-three percent. That's staggering. And it's probably underreported because people don't want to be seen as difficult. Lucas: Exactly. So let's talk about why this happens. It's rarely pure malice. A lot of managers feel pressure to look competent and idea-rich. When they hear a good idea, their instinct is to absorb it — not out of greed, but out of survival. They're afraid of being seen as someone who doesn't contribute. Luna: So it's insecurity disguised as leadership. Lucas: Precisely. And if you understand that, you can respond in a way that helps them save face while still getting your due. The key is to not frame it as 'you stole my idea.' Instead, you frame it as collaboration. Luna: Okay, I'm listening. What does that look like in practice? Lucas: The simplest move is the 'innocent clarification.' Right after your boss presents your idea as theirs, you say, 'I'm glad you liked that approach I shared last week. I think we can build on it further by adding X.' You're not accusing. You're just linking the idea back to you, while also adding value. Luna: I like that. It's not confrontational. It's almost like you're agreeing with them, but you're also establishing provenance. Lucas: Exactly. And it works because most bosses will let it slide — they get that you're not challenging their authority. In fact, a smart boss will even reinforce it, like 'Yes, great idea from Lucas.' But for that to work, you have to have documented the idea beforehand. Luna: You mean like sending an email or putting it in a shared doc? Lucas: Exactly. If you pitched the idea in writing — even a quick Slack message — you have a timestamp. In the meeting, you can just say, 'As I mentioned in my note from Tuesday…' That's incredibly hard to argue with. Luna: I used a version of that with that boss I mentioned. After she presented my slide, I started keeping a shared Google Doc called 'Project ideas and progress' that I would update before every meeting. It had timestamps and my name next to each entry. The next time she tried it, I just said, 'If you look at row 12 in the doc, you'll see the origin of that concept.' She never did it again. Lucas: That's a great example. And you made it a routine — it wasn't accusatory, it was just part of how you worked. Luna: Yeah. And honestly, if today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It keeps the show ad-free and we appreciate it. Lucas: Absolutely. No pressure, but if it helps you navigate a tough boss, that's exactly what we're here for. Luna: So back to documentation — what about people who are in environments where sending a follow-up email feels risky? Like if your boss is the type to get offended by written records? Lucas: That's a real concern. In that case, you can use verbal documentation. After a one-on-one, send a brief summary: 'Thanks for the time. As discussed, I'll work on X and Y, and I'll follow up on the idea we talked about regarding Z.' That way, you've created a paper trail without explicitly calling anyone out. Luna: So you're basically recasting the conversation in a way that attributes the idea to you, but you're framing it as a recap. Lucas: Exactly. And if your boss challenges it, you can just say, 'Oh, I thought that was the direction we were heading. Let me know if I misunderstood.' You're not lying — you're just slightly over-attributing to yourself. And it's very hard for them to correct you without admitting they wanted to take credit. Luna: That's clever. It's almost like a soft boundary. Lucas: It is. And the other tactic is to preempt the theft by making your idea visible to others before the meeting. If you can, share a one-pager or a draft with a few colleagues and cc your boss. That way, when your boss tries to claim it, someone else in the room can say, 'Oh yeah, Lucas sent that around last week.' Luna: So you're using social proof as a shield. Lucas: Exactly. And research backs this up. That same HBR study found that ideas attributed to a specific person in a written format were 60 percent less likely to be misappropriated. The written record is powerful. Luna: What about if you're in a meeting and you don't have any documentation? You've just blurted out an idea on the spot and your boss grabs it. Lucas: Then you pivot to the 'building on' frame. You say, 'Thanks, I'm glad you liked my idea. I think we could extend it by looking at customer retention data. I'll pull that together.' You're reasserting ownership by volunteering to do the work. Most bosses won't stop you. Luna: So you're basically creating a follow-up action that ties the idea back to you. Lucas: Right. And if your boss says, 'No, I'll handle it,' that's a red flag. Then you need to consider whether this is a pattern. If it's a one-off, let it go. If it's the third time, you need to have a private conversation. Luna: How do you have that conversation without accusing them? Lucas: You frame it as a concern about clarity. You say something like, 'I've noticed that sometimes in meetings, my ideas get attributed broadly, and I want to make sure we're tracking contributions accurately so I can develop my thinking. Can we agree to credit ideas to their source in the future?' That's very hard to argue with. Luna: I like that. It's professional and it's about process, not blame. Lucas: Exactly. And if your boss gets defensive, that tells you a lot about their character. Then you have to decide whether to escalate or to just document everything and protect yourself. Luna: I think the most important takeaway is that you have to act quickly. The longer you wait, the harder it is to reclaim. Lucas: Absolutely. The moment you let an idea get stolen without a trace, it's gone. So the next time it happens, try one of these moves. It might feel awkward at first, but it gets easier. Luna: And if all else fails, you can always find a new job. But that's a topic for another episode. Lucas: That is. For now, try the innocent clarification. It's the lowest risk and highest reward move.