A reader asks: how do I handle a peer who keeps taking credit for my work?

The question (paraphrased from r/ProductManagement):

A peer on my team keeps representing our joint work as mostly his. In the last two meetings with our manager, he said “I” where it was “we,” and referenced analyses I did as if he’d done them. Our manager doesn’t seem to notice. I don’t want to be petty, but I’m getting resentful. How do I handle this without blowing up the relationship?

Good news: this is fixable. Bad news: the fix is not “call him out.” Confrontation almost never works for this, because the receipts live in private conversations and your manager will experience the confrontation as you being insecure, not as him being dishonest.

The move is to change where credit gets assigned in the first place, so the crediting problem stops happening.

Why confrontation fails

Three reasons.

1. Your peer can always reframe. “Oh, I meant ‘we’ obviously” or “I was just summarizing — of course you did the analysis” is the standard retreat. You’re stuck looking petty.
2. Your manager can’t adjudicate. He wasn’t in the working sessions. He’s going to hear two versions and pick the easier one, which is “get along.”
3. You look reactive. The quickest way to lose status in a peer dispute is to be the one who brought the dispute into the manager’s office. Seniors notice this.

The better moves all work at the source: they make credit visible before the manager hears the summary.

Three specific moves

Move 1: Document in public

The single highest-leverage thing is to shift your collaboration from private to public. Private conversations are where credit goes missing. Public artifacts are where it sticks.

Specifically:

• Put your drafts in a shared doc with your name on it and share it in the team channel, not via DM. Say “first pass, happy to get Jake’s edits.” Now the team sees the first pass came from you.
• Post updates in Slack, not over the shoulder. “Posted v2 of the model — incorporated the segmentation you flagged yesterday, Jake.” This one line establishes that you built v2 and he flagged one input. It’s not hostile, it’s factual.
• Tag contributors in meeting notes. After a meeting, send a one-paragraph recap with specific attribution. “Jake walked through the revenue framing; I took the action item to pull the segmentation data by Thursday.”

The effect is cumulative. Over two weeks, your manager — and his manager — have a digital trail that says what you did. The “I” vs. “we” language in the meeting no longer controls the picture.

Move 2: Pre-brief your manager

If you have regular 1:1s, use one of them to explicitly frame a project you’re working on.

Don’t say: “Jake keeps taking credit.”

Do say: “I’m running point on the segmentation work for the Q2 review. Here’s where I am, and Jake is helping with the revenue framing. I wanted to make sure you had the picture before Wednesday’s meeting.”

Two things happen. Your manager now has the accurate ownership picture before the meeting, and when Jake says “I” in the meeting, your manager has already primed himself on who did what. This is not sneaky. This is what every senior IC does.

You are not obligated to play the meeting as a neutral observer and hope the manager figures it out.

Move 3: Build with a different peer, visibly

Over the next month, pick one project where you intentionally partner with a different peer, visibly, on something meaningful. Your manager will naturally compare how the two collaborations look.

When the same person (you) is producing good work with two different partners, and one of those partners is openly attributing, it clarifies the signal quickly. Your manager doesn’t need you to tell him what’s happening. He needs to see it with his own eyes.

This takes a couple of months. The payoff is that you stop being dependent on Jake’s crediting for your reputation.

What if your manager still doesn’t see it

If you’ve done all three moves for two months and your manager still credits Jake for your work, the problem is no longer Jake. It’s that your manager isn’t paying attention to attribution, or doesn’t want to.

At that point, you have a manager problem, not a peer problem. That’s a different post. Short version: start building visibility outside your manager — skip-levels, cross-functional partners, a lateral mentor — and make a quiet decision about whether this is the manager you want to be reviewed by next cycle.

What not to do

• Don’t go silent on Jake. If you visibly withdraw from collaboration, you look resentful and petty. Work with him normally. Just change where the work happens — in public, not in DMs.
• Don’t compile a dossier of slights. If your 1:1 with your manager becomes a list of examples where Jake took credit, you will look like the problem. The manager is not going to run forensics on your past meetings. He’s going to watch the next three.
• Don’t match the behavior. The “two can play at this game” version — where you start claiming “I did X” in meetings — makes the whole team look immature and lowers the bar for everyone. Stay one level above.

What this is actually testing

Credit theft is usually about insecurity on the other side, not malice. Jake is probably anxious about his own standing and is compensating. You know this isn’t comforting, but it matters because it means you don’t have to play this as an adversarial game. You can play it as a reputation-building game. The public-documentation move is the same whether Jake is malicious or anxious, and it works either way.

Edge cases

• If Jake is explicitly senior to you, lean harder on the pre-brief move and the shared-doc move. Do not try to build with “a different peer” at a lower level — it can read as grandstanding.
• If you’re on a small team (three or four people), the social cost of confrontation is higher and the public-documentation move is even more important. The entire team sees the trail.
• If Jake is a friend outside of work, say something privately, once, low-stakes: “Hey — small thing, but it would help me if you said ‘we’ more in those meetings with [manager]. I want to make sure my contribution is visible.” Then drop it. If the behavior continues, the friendship isn’t actually helping you here.

Do this today

Find the last piece of shared work you did with Jake. Turn it into a public artifact: post the summary in the team channel, tag him on the parts he contributed to, and put your name on the parts you did. Not as retaliation. As a new default.

For the status-update rhythm that makes credit attribution automatic over time, use the status update template. For the healthier version of workplace competition that avoids spirals like this one, see workplace competition: healthy hustle vs. toxic tug-of-war.

—

If you have a question like this, send it in and it may become a Reader Q column. Anonymity guaranteed.