Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / When A Colleague Takes Credit for Your Work
Transcript
- Lucas: You present a solid idea in a Tuesday morning team meeting. You frame it clearly, you reference the data you pulled together the night before. Your manager nods, says 'interesting,' and moves on. Two weeks later, you're in an all-hands presentation and that same manager is on stage, pitching your idea to the C-suite — without your name anywhere near it. Luna: That specific gut-punch feeling — I think almost everyone listening has felt it at least once. And it's tricky because your first instinct is usually either to say nothing or to confront them publicly. Both are risky. Lucas: Right. So today I want to walk through a real case and then a few practical ways to handle this without torching your career. The case comes from a mid-sized tech firm in Austin. A junior analyst named Priya had been building a competitive analysis on a pricing shift in their segment. Her manager, let's call him David, gave her the project. She delivered a 40-page report with clear recommendations. Luna: And David presented those recommendations to the VP of product — verbatim, in a strategy deck — with his name on the cover. Priya found out from a colleague who was in the meeting. Lucas: Exactly. And this is where a lot of people make a mistake. They either ghost the manager and start job-hunting, or they send an email to the VP saying 'actually that was my work.' Both approaches have real downsides. Quitting prematurely leaves your reputation in someone else's hands. Escalating without evidence often makes you look like a complainer. Luna: And the manager will usually deny it or say 'I built on her thinking' — which is a classic move. So what did Priya actually do? Lucas: She did something smarter. She scheduled a one-on-one with David and framed it as a follow-up on the analysis. She said: 'I noticed my pricing recommendations were featured in the VP deck. I'm glad they landed well. Can we talk about how I can be more involved in presenting that work going forward?' Luna: That's really good. She didn't accuse him. She stated the fact — 'I noticed' — and redirected toward future visibility. That keeps the conversation collaborative and puts the ball in his court. Lucas: David actually did something interesting in response. He acknowledged her contribution and said 'you're right, I should have looped you in.' He then invited her to co-present the next phase to the VP. So in that case, it worked. But not every manager responds that way. Luna: And honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It's what keeps this show ad-free and independent. Lucas: Yeah, listener support makes a real difference. We try to keep every episode practical, and knowing people find value in it — that's the fuel. So if you're able, that link is buy me a coffee dot com slash fexingo. Luna: Alright, back to Priya's case. Not every scenario ends with a cooperative manager. What happens when the manager doubles down? Lucas: That's where you need a different playbook. I want to talk about two things: documentation and selective battles. First, documentation. Before you share any substantial idea in a meeting, send a brief email to your manager or the team — 'here's a summary of the analysis I'm working on, would love feedback.' That creates a paper trail with a timestamp. Luna: Right, so it's not about being paranoid. It's about creating a record of your thinking before it gets absorbed into someone else's narrative. Lucas: Exactly. And second, selective battles. There's a difference between a one-time oversight and a pattern. If a manager consistently takes credit for your work — and research from one organizational behavior study I saw showed that teams with systemic credit misattribution have 23 percent lower retention within 12 months — then you need to escalate, but carefully. Luna: I'd push back a little on the 'your own responsibility' framing that sometimes comes up in this conversation. People say 'you should have made yourself more visible.' But when there's a power imbalance — a manager versus a junior analyst — the junior doesn't always have the platform to self-promote. The structure of the meeting, the agenda, who gets to speak — those are controlled by the manager. Lucas: That's a fair point. So the advice to 'just speak up more' is incomplete. What matters is creating a structure where your contribution is visible to people beyond your direct manager. One tactic: after a project, send a recap to a wider group — including your skip-level — crediting the team but also noting your specific role. CC your manager so it's transparent. Luna: And if the manager objects to that? Says 'why are you sending that to the VP?' Lucas: Then you have a bigger problem, and that's a signal that your manager is actively trying to control your visibility. That's when you might consider whether this is a sustainable environment. But the key is to act before the pattern is entrenched. Most people wait until they're furious, and by then the window for a calm conversation has passed. Luna: Let's talk about the confrontation script for when you do need to address it directly. What do you say? Lucas: I like a three-part structure. One: state the fact neutrally. 'I noticed my analysis from last month was included in the Q3 strategy deck.' Two: express your goal. 'I'd love to be more involved in presenting that work going forward.' Three: offer a solution. 'Could we set up a quick review before the next deck goes out so I can add context?' That frames it as process improvement, not grievance. Luna: And if the manager says 'I built on your idea, it's different now'? That's a common deflection. Lucas: Then you get curious. You say 'I'd love to understand how you evolved it — can you walk me through the changes?' That forces them to articulate what they added. Often they can't. And if they can, you learn something. But the act of asking shifts the dynamic from passive to active. Luna: One more thing I think is worth mentioning: peer credit-stealing. It's not always the manager. Sometimes it's a colleague at the same level who paraphrases your idea in a meeting and gets the nod from the boss. Lucas: Yeah, that's actually more common in flat organizations or matrixed teams. The approach there is slightly different because you don't have the power dynamic. You can be more direct. 'Hey, I noticed you mentioned the automation idea in the stand-up — I'd been working on that. Let's sync up so we're aligned on who's doing what.' That draws a boundary without accusing. Luna: And if it keeps happening with the same person, you might want to involve your manager — not to tattle, but to ask for guidance on coordination. 'I'm finding some overlap with Sarah on project X. Could we clarify ownership?' That's a neutral way to escalate. Lucas: Exactly. The through-line in all of this is: don't let the first instance define the relationship. Give people a graceful way to correct. Most credit-stealing is born from sloppiness or over-eagerness, not malice. But if the pattern persists, your next move isn't confrontation — it's exit planning. Luna: That's a good note to end on. Priya stayed at that company another year, got promoted, and David actually became an advocate for her because she handled it professionally. But the key was she addressed it early, before resentment built up. Lucas: And that's really the lesson. You protect your career not by fighting every battle, but by building systems — documentation, visibility, direct but gracious conversations — that make it harder for your work to be erased. Thanks for listening, and we'll talk to you next time.