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 Public
Transcript
- Lucas: You're in a meeting. Your boss stands up, presents your idea, gets the applause. Your name never comes up. That moment — the credit theft — it's one of the most corrosive things that can happen to your motivation and your career trajectory. Luna: It's also incredibly common. I think almost everyone who's worked in an office for more than a couple of years has a story like that. Lucas: Right. And the standard advice — 'keep a brag file,' 'document everything' — it's usually incomplete. It doesn't tell you what to do in the moment or in the 24 hours after. So let's look at a real case. A marketing analyst named Priya. She worked at a mid-size tech company, about 300 people. She'd spent two weeks building a campaign strategy for a new product launch. Luna: And her director — let's call him Mark — he had her present it to him privately. She walked him through the whole deck. Lucas: Exactly. Mark nodded, asked a few questions, said 'good work.' Two days later, there's a leadership offsite. Priya isn't invited. But Mark presents her strategy to the C-suite. He frames it as his own thinking. The CEO says 'great idea, Mark.' Priya hears about it from a friendly VP who was in the room. Luna: That's brutal. And the natural impulse is to either confront Mark directly or just seethe and do nothing. Lucas: Both of which have high costs. Direct confrontation can brand you as difficult — especially if your boss is well-liked. Doing nothing means it will almost certainly happen again. So there's a middle path. I want to walk through three specific tactics that Priya could have used, and that anyone in that situation can use. Luna: Okay, lay them out. What's the first one? Lucas: First: public attribution seeding. Before you share an idea with your boss one-on-one, you want to create a small public record. The simplest version is sending a brief email to your boss and copying one other person — maybe a peer or a supportive colleague — with a subject line like 'Thoughts on the Q3 campaign direction.' The body is just one or two sentences outlining the core idea. It's not a full deck. It's a breadcrumb. Luna: So later, if your boss presents it, you have a timestamped record that you originated the thinking. Lucas: Exactly. And it doesn't have to be confrontational. You can frame it as 'wanted to get your early thoughts before I build this out.' That's reasonable. Priya could have done that easily. Luna: But what if the boss says 'don't cc anyone else, just send it to me'? That's a red flag in itself. Lucas: Big red flag. If your boss actively wants no witnesses to your ideas, that tells you something about their intentions. In that case, you might skip the seeding and go straight to tactic two. Luna: What's tactic two? Lucas: The meeting follow-up with written breadcrumbs. So the incident has already happened. Mark presented Priya's idea. Priya doesn't confront him. Instead, she sends him an email the next morning. She writes something like: 'Really glad to hear the Q3 campaign concept was well-received at the offsite. I'd love to start building out the execution plan based on the framework I shared with you earlier this week. Can I schedule time to walk through the next phase?' Luna: That's smart. She's not accusing him. She's claiming ownership of the execution phase, and she's very politely reminding him that the idea came from her — all in writing. Lucas: Right. And if Mark responds positively, she's now the owner of the project. If he responds poorly — or ignores it — she has a paper trail that says 'I originated this, and he's now blocking me from working on it.' That's useful if she needs to escalate later. Luna: What about the moment itself? If you're in the room when your boss presents your idea without credit — do you say something then? Lucas: That's tactic three: the strategic re-insertion. You don't blurt out 'that was my idea.' That sounds petty. But you can say something like: 'I'd love to build on that. When I was researching this approach last week, I found some data on customer acquisition costs that could strengthen the rollout plan.' Luna: So you claim authorship indirectly, by showing depth of knowledge that only the originator would have. Lucas: Exactly. You're not fighting for credit. You're demonstrating expertise. And the people in the room — especially senior leaders — they notice. They think, 'Oh, this person really knows this topic.' It shifts the perception of ownership without a confrontation. Luna: I like that. It's subtle but powerful. And it works best if you have a reputation for being prepared and data-driven already. Lucas: Absolutely. The re-insertion only works if you're seen as credible. If you're the person who never speaks up, suddenly claiming expertise can look like grandstanding. So part of this is building a baseline of visibility — asking smart questions, sharing insights regularly — so that when you do step in, it lands naturally. Luna: Let's talk about the psychology of the boss who does this. Why do they steal ideas? Is it always malicious? Lucas: I think it's usually insecurity. A boss who feels threatened by a talented direct report might subconsciously absorb the idea as their own. Or they might genuinely think 'this is my team, so their ideas are my ideas.' But the effect is the same. And sometimes it's just sloppiness — they're so focused on the presentation that they forget to credit the source. Luna: But sloppy or malicious, the damage to your career is real. If your name isn't attached to your work, you don't get the promotions. Lucas: Right. And that's why you need a strategy before it happens. The three tactics are a toolkit. You don't use all of them at once. You pick the one that fits the situation. Priya could have started with the follow-up email. If that didn't work, she could have escalated to the friendly VP she had. Luna: And if the VP is complicit or useless? Then you're looking at a cultural problem, not just a bad boss. Lucas: That's the threshold for leaving. If you've done the seeding, the follow-up, the re-insertion, and you've tried to build lateral visibility with skip-level leaders, and it's still happening — the organization rewards credit theft. That's a structural issue. No amount of managing up will fix it. Luna: So the decision to stay or go is a separate conversation. But for someone in the thick of it, the tactics give them agency. They're not just a victim. Lucas: Exactly. And that's the core of managing up — it's not about pleasing your boss. It's about protecting your career trajectory while still doing good work. The tactics work because they're professional, they're evidence-based, and they don't escalate unnecessarily. Luna: One thing I'd add: if you have a good relationship with a peer who was in the meeting, you can also ask them to help seed attribution. Like, 'Hey, when you talk to the VP about the campaign, could you mention that the original framework came from me?' Lucas: That's a great addition. Allies matter. And if you have a network of people who respect your work, you're much harder to erase. Luna: Speaking of respect for the work — if we've helped you think about a tricky boss situation, or given you a script you actually used, that's exactly why we make this show. It's listener-funded, no ads, no sponsor pressure. A few hundred of you chip in each month through buy me a coffee dot com slash fexingo, and that's what keeps the episodes coming. So if the show's been useful to you, that's the way to keep it going. Lucas: Yeah, and we mean that. It's a small group, but it makes a big difference. Alright — back to the tactics. One nuance I want to add: timing matters with the re-insertion. If you do it too early in the meeting, it can seem like you're trying to hijack the conversation. If you do it too late, the moment has passed. Luna: What's the sweet spot? Lucas: Right after the boss finishes explaining the idea, before anyone else reacts. You jump in with 'That's a great direction — when I was working on the research for that, I noticed...' It's seamless. It feels like you're building on the idea, which you are. But you're also anchoring yourself as the person who did the groundwork. Luna: And if the boss tries to cut you off or move on quickly? That's another signal. Lucas: It is. And then you have data for the next step — maybe a private conversation with your boss where you say, 'I noticed in the meeting you didn't mention my involvement in the campaign strategy. That was my work, and I'd like to make sure going forward that I'm credited, especially when it's presented to senior leadership.' That's a direct, professional conversation. And if it goes badly, you escalate. Luna: You've mentioned escalation a couple times. What does that look like in practice? Lucas: Ideally, you go to your skip-level — your boss's boss — or HR. But you don't go with a complaint. You go with a pattern and a request. 'Over the last three months, on three separate occasions, my director has presented my work without attribution. I've tried addressing it directly. I've tried documenting it. I'm concerned that this is affecting my ability to be evaluated fairly. Can you help me find a way to ensure my contributions are visible?' Luna: That's hard to dismiss. You're not attacking anyone. You're asking for a process fix. Lucas: Exactly. And if the organization has any interest in retention and fairness, they'll take that seriously. If they don't — well, that tells you something about the organization. Luna: I think the biggest takeaway from today is that you can't prevent idea theft entirely, but you can make it much harder for your boss to do it without consequences. Lucas: Right. The goal is not to eliminate the risk — it's to create enough visibility and documentation that the theft becomes costly for the thief. And that's a form of power you can build, regardless of your title. Luna: And if you're listening and you've been through this, what worked for you? We'd love to hear it. Lucas: Yeah, drop us a note. We read every one. And in the meantime, try one of these tactics next time you see it coming. You'll be surprised how much control you actually have.