How to Handle an Employee Who Takes Credit for Other People's Work

You’re in the weekly team meeting, looking at a slide with a beautiful, clear data visualisation. And you feel a familiar tightening in your chest. Mark is talking, using the word “I” as he walks everyone through the analysis. “As I dug into the numbers,” he says, “I realised we had the story backwards.” The problem is, you know for a fact that Sarah built this slide. You saw the drafts. You gave her feedback on it yesterday. Everyone else is nodding along, impressed. You want to interrupt, to say, “Mark, wasn’t it Sarah who found that insight?” But you don’t. It feels too confrontational, too much like a public shaming. Instead, you just sit there, your frustration building, while you mentally type into a search bar: "employee keeps taking credit for my team's work".

This situation feels intractable because it’s not a simple communication problem; it’s a systemic trap. The structure of most team projects creates an “ambiguity shield” that the credit-stealer uses to their advantage. Because work is collaborative, they can frame their actions as summarising, presenting, or “building on” the team’s effort. Any attempt to call them out directly can be easily deflected (“Of course Sarah helped! It was a team effort!”). This puts you, the manager, in a double bind: either you let the behaviour slide and watch your best people grow resentful and disengaged, or you intervene and risk looking like you’re playing favourites or creating unnecessary drama over something that is plausibly a misunderstanding. The path of least resistance is to do nothing, and that’s precisely what keeps the pattern locked in place.

What’s Actually Going On Here

The employee who takes credit for others’ work thrives in environments where contributions are poorly defined and recognition is verbal and informal. They exploit a cognitive bias in their audience: we tend to associate the person presenting the information with the person who generated it. When Mark stands at the front of the room explaining a slide, the team’s mental shortcut is to assign him ownership of the idea, even if they vaguely remember Sarah working on it. The credit-stealer doesn’t need to lie outright; they just need to occupy the airspace.

This is reinforced by a pattern you might call the “Quiet Contributor and the Loud Narrator.” The quiet contributor (Sarah) is often head-down, focused on doing excellent work. She believes the work should speak for itself. The loud narrator (Mark) is focused on making sure his perceived contributions are visible and celebrated. He spends his energy crafting a story about the work in which he is the protagonist.

Your organisation, without meaning to, likely rewards the loud narrator. In meetings, the person with the most confident narrative gets the positive attention. When senior leaders ask for an update, they talk to the person who is most eager to give it. Your inaction as a manager completes the circuit. By failing to correct the attribution, you silently validate the narrator’s version of events. Sarah learns that her good work isn’t enough; it will simply be absorbed into Mark’s personal brand. Her motivation plummets.

What People Usually Try (and Why It Backfires)

When faced with this frustrating loop, managers tend to make a few logical-but-flawed moves that only reinforce the problem.

• The Vague, All-Hands Announcement. You say something in a team meeting intended to be a course correction for one person.

  “Just a reminder, let’s make sure we’re giving credit where it’s due. Teamwork is really important.” This backfires because it’s unactionable. The person taking credit hears it and thinks, “Good point. I’m a great team player.” The person whose work was taken feels unseen and patronised, thinking, “My manager sees the problem but refuses to actually deal with it.”

• The Private Consolation. You pull the quiet contributor aside after the meeting to reassure them that you see their real contribution.

  “Hey Sarah, I know you were the one who did all that data work. Great job. I see you.” While well-intentioned, this is a form of abdication. You are validating her frustration but signalling that you aren’t willing to have the difficult conversation with Mark. You’ve made her feel heard, but you’ve also made it her problem to live with.

• The Ambush 1-on-1. You bring it up with the credit-stealer directly, but you do it based on a feeling or a general observation.

  “Mark, I feel like you’re not always sharing the spotlight. It seems like you’re taking credit for other people’s work.” This immediately puts them on the defensive. Because you’ve framed it as a character judgment (“you are a credit-stealer”), they can easily push back using the ambiguity shield: “I never said I did it alone! I’m the one presenting, so I say ‘I.’ It’s just how I talk.” The conversation devolves into a messy argument about intent, and you walk away with no change in behaviour.

A Different Position to Take

To break this pattern, you have to shift your role. Stop being the secret keeper of who really did what, and stop being the referee of interpersonal conflict. Your job is not to fix the credit-stealer’s personality. Your job is to become the Architect of Clarity.

From this position, your primary goal is to change the system, not the person. You are redesigning the team’s processes to make ambiguity impossible. You will create structures where credit is so clearly and publicly assigned that it cannot be easily stolen. This means letting go of the need for the offender to have a moment of self-realisation or to apologise. You are no longer managing their intentions; you are managing their observable behaviour by changing the environment they operate in.

You stop correcting the record after the fact and start structuring the workflow so credit is clear from the beginning. The goal is to structure how your team works so that individual contributions are visible and assigned by default, from the moment a project starts until it’s finished. You aren’t hunting for culprits; you are building a system where credit is a natural, visible output of the work itself.

Moves That Fit This Position

These are not scripts to be memorised, but illustrations of how an Architect of Clarity operates.

• Assign ownership at the start, not the end. In the project kickoff meeting, define not just tasks, but who will be the public owner of each component.

  “For this client proposal: Sarah, you are owning the competitive analysis section, slides 4-7. Mark, you’re owning the executive summary and the implementation timeline, slides 1-2 and 8. When we present this internally next week, I want each of you to speak to the slides you own.” This move preempts the land grab. Ownership is designated publicly and prospectively.

• Narrate the work in public. Use your authority as the manager to consistently and specifically attribute work where it belongs in team meetings and updates.

  “Quick update on the Q3 report. The team has made great progress. I want to call out the fantastic work Sarah did on the user survey analysis, that key insight on page 5 came directly from her. Mark did a great job of integrating that into the main project narrative.” This models the behaviour you want to see. It corrects the record without a direct confrontation and creates a public ledger of contributions.

• Give direct, behavioural feedback. When you do need to speak with the credit-stealer, don’t talk about their attitude or intent. Talk about specific, observable actions and state the required change.

  “Mark, I want to talk about the client presentation yesterday. When you went through the budget slides, you used the phrase ‘the numbers I ran.’ My project notes show that Sarah was assigned that work. In all future presentations, when you are presenting work done by a teammate, I need you to explicitly state their name. Say, ‘Here’s the analysis Sarah put together,’ not ‘Here’s the analysis I did.’” This is non-negotiable. It isn’t an accusation; it’s a clear, operational directive. It’s not about how he feels, it’s about what he does.