A reader question that arrives weekly in some form: "My manager presents my work as his own. Do I confront him?"
No. Not because confrontation is scary, but because it structurally fails. Play it forward: you raise it, he says "we're a team here", you look precious, and the exec still doesn't know your name. You've spent capital and bought nothing. Today's edition is the protocol that works instead.
First, the framing you need
Your manager presenting your team's work is partly the system operating as designed. The layer above expects a manager to curate their team's output; that's the deal. The problem is not that your work travels under their voice. The problem is that your authorship evaporates in transit. Different problem, different fix: you don't stop the work travelling, you make it travel with your name attached. Credit is far easier to keep than to reclaim, so every move below happens before the work leaves you, not after.
Move one: name the artefact
Your name and date on the front of everything you produce. Standard professional practice, zero drama, and surprisingly rare. Documents move through organisations carrying whatever attribution they left with. A named document can be presented by anyone and still builds your record. An unnamed one builds the presenter's.
Move two: offer the assist
When your work is heading upward in someone else's hands, one sentence: "Happy for you to lead it. Want me there for the detail questions?" This nearly always gets a yes, because detail questions are precisely what the presenter fears. Now the room watches you handle the substance live, which is the strongest form of exposure there is (day 3), and it happened as a favour to your manager rather than a challenge.
Move three: build the second channel
Mention the work, lightly, to one stakeholder outside your reporting line: "Let me know if the analysis I built lands well with your team." One sentence, one witness. Your authorship now exists in two independent locations, and quiet erasure has to fail in both. This is the same redundancy principle engineers use, applied to reputation.
Move four: keep the log
Every contested-credit situation eventually comes down to records. Your evidence file (day 2) with dates is not for a courtroom showdown; it's for your review, your calibration sentence (day 4), and your own certainty when self-doubt arrives at 11pm.
The escalation clause
If the pattern continues after a quarter of the protocol, the conversation is now worth having, and from much stronger ground: "I want to make sure my contributions are visible when work goes upward. Can we agree how attribution works?" Note what changed: you're not litigating the past, you're setting a rule for the future, and you have a quarter of named artefacts demonstrating you mean it.
Why this compounds
Run consistently, the protocol produces a quiet shift: senior people start contacting the author directly, because they've now seen where the substance lives. Questions begin routing around the presenter to you. That's not revenge. It's just information flow correcting itself once accurate attribution exists.
Your assignment
Name and date the next thing you produce, and make the assist offer on the next piece of your work that's travelling upward. Both this week.
Talk soon, Yasar
P.S. Got a version of this situation? Reply with it. A reader question runs most weeks in this series.
