What nobody tells you
- Most credit-stealing isn't a grand conspiracy — it's often a habit of sloppy pronoun use ('I did X') that nobody's ever called out.
- Documentation before the fact is far more powerful than complaints after the fact.
- Addressing it directly with the person, calmly, resolves it more often than people expect — public confrontation should be a last resort, not a first move.
The basics
- There's a difference between someone summarizing team work loosely ('we shipped X') and someone specifically claiming your individual contribution as their own.
- The best prevention is proactive visibility — sharing your own updates and being cc'd or present when work is discussed — not just reacting after credit is taken.
- Escalating to a manager works best when you bring specific, dated evidence, not a general complaint about feeling overlooked.
The framework
Prevent, Address, Escalate
A three-tier response, used in order, matched to how persistent the problem is.
- 01
Prevent: build visibility for your own work before credit disputes can even arise.
- 02
Address: raise it directly and specifically with the person, assuming good faith the first time.
- 03
Escalate: if it repeats, bring dated, specific evidence to a manager.
The playbook
The conversation — what to actually say
Addressing it privately with the colleague
“I noticed the update described this project as yours — I led the analysis and wanted to flag that so it's accurately reflected going forward.”
Correcting it live in a meeting
“Just to add some context — I led that specific piece of the analysis.”
Escalating to a manager after repeated instances
“I want to flag a pattern, not one incident: here are three dated examples where my contributions were attributed elsewhere. I'd like your help making sure the record is accurate.”
The mistakes — what people get wrong
- Staying silent every time to avoid seeming petty, until the pattern becomes the accepted narrative.
- Confronting the person publicly and aggressively the first time, before assuming good faith.
- Escalating with only a vague feeling instead of specific dated instances.
- Not building your own visibility proactively, relying entirely on others to represent your work fairly.
Ask yourself
- Is this a one-off sloppy summary, or a repeated pattern?
- Have I made my own contributions visible in real time, or only after the fact?
- Do I have specific, dated examples if I need to escalate?
Go deeper
- Book
Crucial Conversations — Patterson et al.
Framework for addressing sensitive issues directly without escalating conflict unnecessarily.
- Practice
The real-time update habit
Send your own brief progress notes so your work is visible as it happens.
- Exercise
The contribution log
A simple running record of who did what on shared projects.
General educational information, not legal, tax, medical, or financial advice. Rules vary by country and change over time — verify with a qualified professional before acting.