Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Respond When a Colleague Takes Credit for Your Work
Transcript
- Lucas: So you present a full campaign analysis in a meeting, and your boss says 'great work, Jen' — and you're not Jen. Jen is the colleague who contributed one data point two weeks ago. Luna: Oof. That's the specific gut-punch we're talking about today. Lucas: We got an email from a listener named Priya at a mid-size marketing agency. She spent three weeks building a competitive landscape report. Her colleague, Derek, presented it to the VP of Strategy and never once said her name. Priya found out from a Slack channel where someone congratulated Derek. Luna: And she's wondering whether to confront Derek, talk to the VP, or just let it go. What's the right move? Lucas: First move: document. Priya should pull the email thread where she shared the draft with Derek, save the Slack messages where she outlined the methodology, and note the timestamp on the original file. If this ever escalates, you want a paper trail, not a memory. Luna: But she doesn't want to look like she's building a legal case against a teammate. Lucas: Right, so you keep that documentation private. It's insurance, not ammunition. Second move: she needs to decide whether this is a pattern or a one-off. Derek might have just had a brain freeze under the VP's pressure. Luna: I think that's generous, but possible. If it's the first time, you can address it one-on-one. Lucas: Exactly. Priya could say, 'Hey Derek, I noticed in the VP meeting you presented the competitive landscape work. Because I led that analysis, I'd appreciate if you could mention my contribution next time. Happy to share the slide deck if that helps.' No accusation, just a clear expectation. Luna: And if Derek gets defensive? Lucas: Then you have your answer: it's a pattern. At that point, Priya should schedule a brief chat with the VP, framed around team visibility — not Derek-bashing. Something like, 'I want to make sure our team gets full credit for the cross-functional work we're doing. I led the competitive landscape piece and I'd love to present the next update directly.' Luna: That's smart because it positions her as someone who cares about team outcomes, not personal credit. Lucas: Right. And the VP will almost certainly say 'of course, send me the deck.' Now Priya's name is in front of a senior leader without a single negative word about Derek. Luna: What if the VP doesn't seem to care or brushes it off? Lucas: Then it's a culture signal. If leadership doesn't reward attribution, the problem is bigger than Derek. Priya can start keeping a 'brag sheet' of her contributions and look for opportunities to present directly in team meetings. And frankly, she might want to update her resume. Luna: So the framework is: document, address directly once, escalate to a higher-up only if the pattern continues, and frame it around team success. Lucas: Exactly. And one more thing: if Priya confronts Derek and he apologises and says it was an honest mistake, I'd give him the benefit of the doubt once. People are human. But I'd also proactively cc Derek on future project emails with the VP, so there's a visible record of who's doing what. Luna: That's a low-friction way to prevent it from happening again. Lucas: Now, I want to circle back to something. We get a lot of messages from listeners who say these episodes have helped them navigate real situations at work — and honestly, that's why we do this show. If you've gotten something out of it, a couple of dollars a month is genuinely what keeps these going. You can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small gesture that makes a huge difference for us. Keeps the show ad-free and allows us to dig into the specifics like Priya's case. Lucas: So back to Priya: after she documents and addresses it, what does the follow-up look like? Luna: I think the follow-up is about owning your narrative. If she presents that next update herself, she should explicitly credit the team members who helped — including Derek, if he contributed. That sets a standard of generosity that leaders notice. Lucas: That's a power move. By giving credit publicly, you become the person who elevates others. And if Derek keeps taking credit anyway, he looks petty by contrast. Luna: I've also seen people use a simple technique in meetings: after someone presents your work without naming you, you can chime in with, 'Thanks for including that analysis, Derek. I found the data on customer churn especially interesting because it correlates with the Q2 retention drop. Happy to walk through the methodology if anyone wants.' Lucas: That's smooth. You're not saying 'hey, that was mine.' You're adding value and implicitly restaking your claim. Luna: Exactly. And if the culture is healthy, someone will pick up on it. Lucas: Let's talk about when to walk away. If Priya has tried the direct conversation, the VP chat, and the public restating, and nothing changes — she's in a system that rewards credit takers. That's not a fixable problem at an individual level. Luna: And that's hard to hear, but sometimes the best career move is to leave a place where your contributions aren't seen. Lucas: But before she leaves, she should make sure her resume and LinkedIn reflect the work she actually did. Use phrases like 'led the competitive landscape analysis that informed the Q3 strategy' — that way future employers see the scope, even if her current boss didn't. Luna: And she can ask colleagues who witnessed her work to write LinkedIn recommendations or be references. Lucas: Right. The key takeaway for Priya — and anyone in her shoes — is that credit theft is less about your worth and more about the other person's insecurity or the culture. But you have tools to reclaim visibility, and if those tools don't work, you have the power to walk. Luna: And document everything along the way. That's the thread that runs through all of this. Lucas: Alright, that's our time for today. Good luck out there.