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: You present a brilliant idea in a meeting. Your boss nods, takes a note. Three weeks later, a colleague presents the exact same idea — word for word — and gets a promotion. Today we are talking about what to do when someone steals your work. Luna: I have been there. It is infuriating. And the worst part is, if you react emotionally, you look petty, not wronged. Lucas: Exactly. So we got an email from a listener — let us call her Priya. She is a marketing manager at a mid-size tech company. She spent three weeks building a campaign strategy for a new product launch. She presented it to her team. Her junior colleague, let us call him Raj, said nothing during the meeting. Two weeks later, Raj presents the same strategy — with Priya's exact slides — to the VP of marketing. He gets a shout-out in the company all-hands and is assigned to lead the campaign. Priya gets nothing. Luna: Ouch. I would have been livid. What did she do? Lucas: She sent an email to her boss — who had been in the original meeting — saying, 'Hey, I noticed Raj presented the strategy I shared earlier. Just wanted to clarify the work was mine.' Her boss replied, 'I am sure it was a coincidence. Let us move forward.' And nothing changed. Luna: So the email backfired. She looked defensive, and her boss dismissed it as a misunderstanding. Lucas: That is exactly what happens in most cases. So let us talk about a better approach. The first thing to understand is that credit theft is rarely a single event. It is a pattern. And your response should depend on whether this is a first-time incident, a repetition, or a systemic issue. Luna: So you are saying not every stolen idea requires a confrontation. Lucas: Right. If it is the first time, your goal is not to punish — it is to establish a trail. The best move is not an email to your boss. It is a live, public correction in the next meeting where the same topic comes up. You say something like, 'I am glad that the framework we developed together is getting traction — I have some additional data on that if you want to hear it.' Luna: That is smooth. You are not accusing anyone. You are simply reminding the room that you were part of the creation. Lucas: Exactly. And if your colleague then says, 'Oh, yes, we collaborated on that,' you have just re-established shared ownership without a fight. But if they double down and say, 'Actually, this was my idea,' then you have a data point. Luna: What about the second time? When you see the pattern forming. Lucas: Second time, you move to a private conversation with your colleague. Not accusatory. You say, 'I noticed that my research on the Q3 campaign made it into your presentation. I want to make sure our contributions are clear going forward. In the future, could we agree to mention each other by name when we build on each other's work?' Luna: That puts the ball in their court. If they react defensively, you know it is deliberate. Lucas: Right. And at that point, you have a decision to make. If the colleague is a repeat offender and above you in rank, you may need to escalate. But here is the key: escalate with evidence, not emotion. You collect specific examples — dates, meetings, documents. And you frame it as a concern about team collaboration, not a personal grievance. Luna: I want to add something here. There is a tactic that works before the theft ever happens. In any meeting where you present an idea, ask a question that forces the group to attribute the idea to you. Like, 'Can we all agree that the starting premise — which I put together — is sound before we move to execution?' Lucas: That is brilliant. You are literally asking for a verbal acknowledgment in the moment. And most people will nod or say yes. Then later, if someone tries to steal it, you have a room full of people who heard you claim authorship. Luna: Yes. And it does not come off as arrogant if you frame it as a procedural check — which is exactly what it is. Lucas: So let us talk about the third scenario: you have tried the public correction, you have had the private conversation, and it happens again. Now you are in escalation territory. Luna: What does that look like? Do you go to HR? Lucas: HR is a last resort, and only if the stolen work had direct impact on your performance review or compensation. Otherwise, you go to your boss — but with a different framing. You do not say, 'Raj stole my work.' You say, 'I want to talk about how contributions are tracked in our team. I have noticed that some of my work has been attributed to others in presentations, and I am concerned that my performance metrics will not reflect my actual output. Can we establish a clearer process for crediting work?' Luna: That makes it about process, not personality. A good manager will take that seriously because it affects team morale and retention. Lucas: Exactly. And if your boss still brushes it off, you have a data point about your boss. Then you have to decide whether this workplace values your contributions enough for you to stay. Luna: That is a hard truth. But I think it is the right one. Priya, our listener, ended up leaving that company six months later. She told us she wished she had escalated earlier instead of sending that email. Lucas: She learned the hard way. But here is the thing — and I want to be honest for a second. This show exists because listeners like Priya send us these questions. And a handful of listeners also support us financially through buy me a coffee dot com slash fexingo. That is what keeps us ad-free and able to do deep dives like this. So if you have gotten value from any episode, that is a way to keep it going. Luna: Yeah, it is a small group, but it makes a real difference. We are grateful. And back to the topic — what about situations where the theft happens in a written format, like a shared document or email chain? Lucas: Good question. Written formats are actually easier to handle because you have a timestamp. If your colleague copies your text from a shared doc and pastes it into an email to your boss, you can simply reply all and say, 'I see you used the analysis from the draft I shared on Tuesday. I have since updated it — let me send you the latest version.' Again, you are not accusing. You are just redirecting attribution. Luna: That also subtly shows your boss that you are the source. And you are being helpful, not territorial. Lucas: Exactly. And one more tactic I want to mention: the 'pre-buttal.' Before a big meeting where you know someone might steal your thunder, send a brief email to your boss or the meeting organizer summarizing your key points. Say something like, 'Looking forward to the meeting. I will be presenting the framework I have been developing, which centers on X, Y, and Z.' That creates a record. Luna: So you are planting a flag before anyone else can. I love that. Lucas: Right. And it does not have to be long. Two sentences. But if someone later claims your idea, your boss can go back to that email and think, 'Wait, Lucas mentioned this first.' Luna: Alright, let us talk about the psychological side. Why do people steal credit in the first place? Lucas: There are a few reasons. Insecurity is the biggest. Someone who feels they are not producing enough original value may take shortcuts. Ambition is another — they want the promotion so badly that they rationalize the theft as 'just using available resources.' And sometimes it is just poor organizational culture. If the company rewards individual heroics over team collaboration, theft is almost inevitable. Luna: So the environment can encourage it. That means your strategy has to account for culture, not just the individual. Lucas: Exactly. If you are in a cutthroat culture, you have to be more defensive. Share your work in smaller pieces. Use written trails. Involve your boss early. But if you are in a collaborative culture, a simple 'hey, let us make sure we are crediting each other' conversation might be enough. Luna: What about the opposite: accidentally overshadowing someone? I have been on both sides, and it feels awful when you realize you may have taken credit without meaning to. Lucas: That is a good point. If you catch yourself doing it — or someone gently points it out — the best move is to publicly correct it. In the next meeting, say, 'I want to give credit where it is due. Luna actually developed the core of that model, and I just built on it.' That builds trust and disarms any resentment. Luna: I think that is the mark of a true leader. People who share credit generously get more in return over time. Lucas: They do. So here is a framework to take away. First time: public re-anchoring without accusation. Second time: private conversation setting expectations. Third time: escalate via process, not personality. And if the culture does not support fair attribution, ask yourself whether this is a place where your work can thrive. Luna: And do not forget the pre-buttal and the live claim. Those are prevention, not cure. Lucas: Right. One final thought. If someone steals your work once, it is a data point. Twice, it is a pattern. Three times, you are the source. Do not let yourself become a permanent source. Luna: That is a good note to end on. Thanks, everyone. We will be back next week with another question.