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

A manager comes to you stuck on one of his people. There is someone on the team, he says, who keeps taking credit for work he didn’t do. The example is always the same shape. A meeting, a polished slide, the man at the front saying “as I dug into the numbers,” when your client knows for a fact that someone quieter on the team built the thing. Your client wanted to interrupt. He didn’t, because it felt like a public shaming over something that was plausibly just a turn of phrase. He has been sitting with the frustration for weeks. The thing to hear underneath the complaint is that he is trying to fix a person, and the case will only move once he stops.

Your client experiences this as intractable because he has it filed as a communication problem when it is a structural one. Most team projects run on shared, blurry attribution, and that blur is what the credit-taker uses. Because the work is collaborative, he can frame what he does as summarizing, presenting, or building on the team. Any direct challenge gets deflected with ease. “Of course she helped, it was a team effort.” That deflection is what puts your client in a double bind. He can let it slide and watch his best people go quietly resentful, or he can intervene and risk looking like he plays favorites and manufactures drama over a misunderstanding. The path of least resistance is to do nothing, and doing nothing is exactly what holds the pattern in place.

What the pattern is actually doing

The person who takes credit thrives in one specific climate. Contributions are loosely defined, and recognition is verbal and informal. Inside that climate he exploits a bias the whole room shares. People associate the person presenting an idea with the person who generated it. When he stands at the front explaining the slide, the team’s mental shortcut hands him ownership, even if they half-remember someone else doing the work. He does not have to lie. He only has to occupy the airspace.

There is a shape worth naming for your client, because once he can see it he stops taking it personally. Call it the quiet contributor and the loud narrator. The quiet contributor stays head-down, doing excellent work, trusting that the work speaks for itself. The loud narrator spends his energy making sure his version is visible and celebrated. He builds a story about the project in which he is the protagonist. Both are doing what comes naturally to them. Neither is wrong inside their own logic.

Here is the part your client will resist hearing. His organization, and his own silence inside it, rewards the loud narrator. The confident narrative gets the attention in meetings. When leadership wants an update, they ask the person most eager to give one. Your client’s inaction closes the circuit. By leaving the attribution uncorrected, he silently ratifies the narrator’s account. The quiet contributor learns that good work is not enough, that it gets absorbed into someone else’s brand, and her motivation drops. The system is doing precisely what it was built to do.

The moves your client has already tried

By the time he reaches you, your client has usually run three plays, all of them sensible, all of them feeding the loop. Walk him through why each one fails before he reaches for it again.

The vague all-hands. He says something in a team meeting meant to course-correct one person. “Just a reminder, let’s give credit where it’s due. Teamwork matters.” It fails because nobody can act on it. The credit-taker hears it and thinks, good point, I am a great team player. The person whose work was taken feels patronized, and reads it as a manager who sees the problem and refuses to touch it.

The private consolation. He pulls the quiet contributor aside afterward to reassure her. “I know you did all that data work. I see you.” Well meant, and a form of abdication. He validates her frustration while signaling he will not have the hard conversation with the narrator. He has made her feel heard and made the problem hers to carry.

The ambush. He raises it with the credit-taker directly, off a feeling rather than a fact. “I feel like you’re not always sharing the spotlight. It seems like you take credit for other people’s work.” This lands as a character verdict, so the man reaches straight for 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 collapses into a fight about intent, and your client walks out with nothing changed.

The shift you coach him toward

The work is to move your client out of two roles he has been playing badly. He has been the secret keeper of who did what behind the slide, and the referee of an interpersonal grievance. Neither role can win. His job is not to fix the credit-taker’s personality. His job is to become the person who builds clarity into the structure.

From that position his aim changes. He stops trying to change the man and starts changing the system. He redesigns how the team works so ambiguity becomes impossible, so credit is assigned publicly enough that it cannot quietly migrate. This means giving up the wish for the offender to have a moment of insight or remorse. Your client is no longer managing intentions. He is managing observable behavior by changing the environment that behavior happens in.

So he stops correcting the record after the fact and starts structuring the workflow so credit is clear from the first day of a project to the last. He is not hunting culprits. He is building a setup where attribution falls out of the work itself.

Language and moves that fit the new position

Give your client these as illustrations of how the position operates, so he can hear the shape and put it in his own words.

Assign ownership at the start. In the kickoff he defines the tasks and then the public owner of each piece. “For this client proposal, you own the competitive analysis, slides four to seven. You own the executive summary and the timeline, slides one, two, and eight. When we present internally next week, each of you speaks to the slides you own.” The land grab is pre-empted because ownership is named out loud and in advance.

Narrate the work in public. Your client uses his own authority to attribute work specifically, in meetings and updates. “Quick update on the Q3 report. I want to call out the work on the user survey analysis. That insight on page five came directly from her. He did a strong job folding it into the main narrative.” This models what your client wants the room to do. It sets the record straight without a confrontation and builds a visible public record of who did what.

Give behavioral feedback. When your client does sit down with the credit-taker, he stays off attitude and intent and talks about a specific action and the change required. “I want to talk about yesterday’s presentation. On the budget slides you said the numbers I ran. My project notes show that work was assigned to her. From now on, when you present a teammate’s work, I need you to say their name. The line is here’s the analysis she put together. The line you used was here’s the analysis I did.” This is not an accusation. It is an operational directive, non-negotiable, about what he does rather than how he feels.

What to listen for in the next session

Notice which role your client reaches for when he reports back. If he describes redesigning the kickoff or correcting attribution in a meeting, he held the new position. If he is back to consoling the quiet contributor in the hallway or rehearsing a speech about the narrator’s character, the old role has reasserted itself and you have something to work in the room.

Listen for whether the behavior changed, separate from whether the man feels chastened. Your client may want the credit-taker to look contrite. The measure is the slide deck and the meeting, the observable thing. A man who keeps presenting but now says her name has given your client exactly what the intervention asked for, regardless of how he feels about it.

Watch, too, for your client’s report that nothing happened because there was no confrontation. That judgment is the referee role trying to climb back in. With this pattern, a project where ownership was clear from the start and never had to be argued over is the project that did its job.

When credit-theft is the wrong frame

Sometimes the man at the front is not taking anything. He genuinely led the work, and the quiet contributor’s sense of being erased is its own piece of work, closer to recognition hunger than to theft. The tell is whether your client’s project notes actually show the work assigned elsewhere, or whether the grievance lives only in how it felt. Take the documented case as a system problem to redesign. Take the felt one as something to explore with whoever feels unseen.

And some of these are not workflow problems at all. When the credit-taking sits inside a culture that openly rewards self-promotion over contribution, or when the leadership your client answers to does the same thing one level up, no kickoff redesign will hold. The structure your client controls is too small for the force acting on it. Most of the time it is not that large. Most of the time he is a manager who has been correcting the record privately and too late, and the work is to move the correction to the front of the project, where it costs nothing and changes the whole pattern.