The email arrives at 4:51 on a Wednesday. Your manager's manager is CC'd. So is the person from finance who controls next quarter's headcount decisions. The subject line says "Quick Update on Project Orion Status," and the body is three paragraphs of careful phrasing that does one thing: it takes the project you built and makes your name disappear from the story.
You read it twice. The first time, your stomach drops. The second time, you start reading architecture instead of words. Who was included. Who was left off. What "team effort" means when one person's name appears in every sentence that contains a verb and yours appears only in the CC line.
Your cursor hovers over Reply All.
Stop. Before you type a single word, you need to understand what just happened, because the obvious read, that someone stole your credit, is accurate but incomplete. What actually happened is that someone tested your response threshold. If you do nothing, the cost of taking from you has been established at zero. If you fire off an emotional correction, you've handed them a gift: you are now the difficult one, and the conversation has shifted from "who did the work" to "why are they so upset about a process email."
Neither silence nor heat. There is a third option, and it has three moves in a specific order.
Move One: Public Competence. Within 24 hours, while the thread is still active in people's inboxes, you reply to the same thread with the same audience. Your reply looks like this:
"Thanks, Diane. Glad to see the Orion work getting leadership visibility. For context, I've attached the project scope I developed in March and the milestone tracker I've been maintaining. Current status: we're six days ahead of the original timeline. Happy to walk through the details in our next check-in."
No adjectives about your feelings. No claims of ownership that sound territorial. What you've done is place documentary evidence into the same thread, in front of the same audience, that makes your authorship a matter of record. The attachment does the heavy lifting. "I developed in March" establishes origin. "I've been maintaining" establishes ongoing ownership. Neither phrase is aggressive; both are load-bearing. Anyone reading the thread now has two versions of the story, and one of them has receipts.
Move Two: Private Boundary. After your public reply has landed and been seen, you send a separate message directly to Diane. Just her. The message sounds like this:
"Hey Diane, wanted to flag something. The email Wednesday framed the Orion work as a team effort that needs leadership alignment going forward. I want to make sure we're on the same page that this project originated from my proposal and I've been the implementation lead throughout. I'd appreciate it if future communications reflect the project history accurately. Let me know if you want to sync."
Most people skip this move entirely, and the skipping is where the pattern gets its oxygen. You are naming the behavior directly, in a private channel, without an audience for her to perform to, without accusation that gives her a reason to escalate. A boundary removes ambiguity that both parties have been navigating around. After you send this, Diane knows you see what happened. She does not know you are angry, because you have not given her that information. What she knows is that you are paying attention and that you have language for it.
Move Three: The Professional Mirror. This only activates if the pattern continues after Moves One and Two. If it happens again, you send a follow-up to Diane, CC your own manager, referencing the specific repeat. The entire sequence tells a story of good faith: you addressed it publicly, you addressed it privately, and you escalated only when the behavior continued.
Three moves. That order. That timing. Move One is public and impersonal. Move Two is personal and private. Move Three is both, and only after the first two were attempted. Each gives the other person a chance to recalibrate, which matters because some credit grabs are unconscious, the product of organizational habits rather than individual strategy.
The sequence works whether the behavior is intentional or not. That is its design.
Practice prompt: This week, find one email thread where your contribution is present but your name is absent. Reply to the thread with a single factual sentence that places your work on the record. Attach evidence if you have it. Notice what happens in your body when you hit send. That sensation is information. Write it down.