It happens in a meeting, usually. Your framework. Your analysis. Your idea - presented as theirs, or as the team's, with no mention of you. Here is what to do and what not to do - from someone who has been on both sides of this.
I was sitting in a leadership review at Zendesk. A manager two levels above me was walking the room through a framework for account segmentation. It was detailed, it was good, and I had built most of it three weeks earlier with two people on my team.
My name was not mentioned once.
I watched my team lead - who had stayed up until midnight two nights running on that work - take this in from across the table. She did not say anything. Neither did I, not in that room.
What I did next mattered more than the meeting.
Why the Immediate Reaction Almost Always Makes It Worse
The instinct in that moment is either to go quiet and seethe, or say something and risk looking petty.
Both are bad moves. Staying quiet does nothing. And publicly correcting a senior person in a meeting - "actually, that was my team's work" - almost never lands the way you want. It makes everyone uncomfortable, including the people you are trying to stand up for. The manager rarely comes off badly in that moment. The person who speaks up often does.
That is unfair. It is also just what happens.
The real conversation needs to happen one-on-one, a day or two later while it is still fresh. Not as an accusation. Just an observation.
"I noticed the segmentation work came up in the review - I would love to make sure the team gets some visibility on things like this going forward. What is the best way to do that?"
That sentence names the issue without making it a fight. It gives the manager a way to respond without getting defensive. And it puts them on notice that you are paying attention, which matters more than any one conversation.
How to Build a Paper Trail That Protects You Without Looking Paranoid
The most durable protection is a record that exists before anyone questions it.
When you finish a significant piece of work, send a short email. Not to stake a claim - just to close the loop. "Wanted to share the final version of the segmentation work - here is what we landed on and why." Copy the people involved. Include your manager.
That email does two things. It creates a timestamp. And it puts what you produced in front of more than one person before anyone has a reason to dispute it.
At Intelegencia, I made it a habit to name the people who did the work in every document - meeting notes, presentations, project summaries. Not as a rule. Because I have been on the other side, and I know what it feels like to watch your work move without your name on it.
The pattern across every team I have been part of is consistent: managers who give credit tend to have teams that go further for them. The ones who take it tend to have teams that start holding back. People track who gets credit for what, even when they say nothing about it.
When the Pattern Repeats and the One-on-One Has Not Worked
If it happens once, it might be carelessness. If it keeps happening after you have said something, that is different information.
At that point the question is not how to fix your manager. It is what staying is costing you.
Your work is your track record. If it keeps disappearing into someone else's portfolio, your career is not building the way you think it is. The people above your manager do not know what you did. The reputation you are spending energy on is landing somewhere else.
I have watched people wait too long on this - people I genuinely liked and wanted to keep. By the time they left, they had spent two or three years building someone else's brand. That time does not come back.
There is a version of this where your manager does not fully understand what they are doing. And a version where they do. Both look the same from the outside for a long time.
The question worth sitting with: how long are you willing to wait to find out which one this is?
