When a Peer Takes Credit for Your Work: 3 Responses, From Subtle to Direct

A few years into a senior PM role, I walked into a performance review proud of about six months of work. Cross-functional research. Stakeholder alignment. A strategy doc with my name all over it. My manager rated the half “average.” The work hadn’t shipped. Hadn’t moved a metric. Nobody was using it. From the inside it felt like a great half. From the calibration room, it didn’t exist.

Credit theft is the social version of that lesson. If your name isn’t legibly on the shipped artifact — the deck, the doc, the recap — someone else’s name lands there by default. And managers grade what they can see.

So when a peer stands up in a meeting and says “I” about a model you built, the instinct is to correct them in the room. Don’t. The room is grading your response more than it’s grading the credit theft. Almost nobody else even clocked it.

Here’s the response ladder. Lightest move first. Escalate only if the pattern continues.

Response #1 — Subtle: re-attach your name to the artifact

First instance, every time. Cost: five minutes.

Send the follow-up. Forward the original deck. Write the recap. Put your name back on the work in a place the right people will see it. You don’t say a word about the credit-grab.

Yes, sending the original deck two days later feels like passive-aggressive credit-staking. That’s because it is. Do it anyway. The person who sends the recap gets credited for running the meeting, regardless of who actually ran it. The person who forwards the source doc gets remembered as the author.

Here is the email I use:

The “attaching the underlying model” line is the whole point. Your name is on the file. The timestamp is on the file. Your manager has a copy of the artifact, not just the meeting story.

Performance reviews are theater. The calibration meeting you’re not in is what your follow-up email is actually for. And the only inputs that conversation has are the artifacts in your manager’s inbox.

Do this once, it’s a recap. Do it after every meeting and over six months it makes you legible.

Response #2 — Direct but private: ask, don’t accuse

Second instance, or the first one where intent looks deliberate. Cost: one slightly uncomfortable conversation.

Put fifteen minutes on the peer’s calendar. Frame the credit-grab as a question, not an accusation:

“Wanted to ask about the share-out yesterday — was leaving my name off the deck intentional, or did it just slip in the edit? I wasn’t sure how to read it.”

Two things happen. If it was accidental, they apologize, they remember, and it stops. If it was deliberate, they know you noticed, and most people will not try it a second time on someone who’s clearly watching.

The question framing matters. You are not asking them to confess. You are giving them a door to walk through that lets both of you keep working together. Jumping to “you stole my work” wins the argument and loses the next two years of being on the same team.

One caveat: this move requires a relationship strong enough to hold a slightly awkward question. If the peer is much more senior, or you’ve been on the team three weeks, skip back to Response #1 and let the artifact do the talking.

Response #3 — Up the chain: escalate with documentation

Third instance, or one truly egregious one, like presenting your deck as theirs to leadership. Cost: a move you can’t take back.

Bring it to your manager. Two rules.

First, lead with impact on the work, not feelings about the peer. “I’m worried about how decisions are getting attributed on this project, and I think it’s going to slow us down on [specific upcoming thing]” lands. “She took credit for my model” doesn’t.

Second, walk in with documentation. The forwarded emails. The original timestamps. The dates of the share-outs. You’re not litigating intent. You’re showing a pattern.

Two outcomes are real here. Escalate well and your manager handles it cleanly. Escalate badly and you get quietly labeled the difficult one. The difference is almost always in the framing and the receipts. If you don’t have receipts yet, you’re still in Response #1 territory. Go build them.

When the ladder bends

• The peer is more senior than you. The ladder collapses to Response #1; the artifact move is the only safe play. Don’t ask a director “was that intentional.”
• The credit-taker is your manager. Different problem, different post. Make your boss shine and find other surfaces for your work.
• Your manager was in the room and said nothing. Almost always inattention, not complicity. Send the recap. It catches both of them up.

---

I’ve watched first-years lose their composure over the first credit-grab and never recover socially from the moment they did. I’ve also watched people swallow ten of these in a row out of “professionalism” and quietly stop being seen as the owner of anything. Neither one is the move.

The move is the artifact. The forward. The recap. The receipt — quietly, three times, until your name is on the work in the room that grades it.

---