If your work keeps ending up under someone else's name, speaking louder in the moment rarely fixes it. What helps is letting people see the work earlier, before anyone writes the summary. Credit gets handed out when someone tells the story of the project. Whoever was in the room when that story took shape usually ends up in it.
That is hard to read if you have been told the answer is confidence.
What is really going on
People do not get credit for effort. They get credit for being easy to remember.
Think about a manager writing a quick update at the end of a busy week. They are writing down the first name that comes to mind, not checking who did what.
So the person who spoke in the meeting where the work got planned is remembered. The person who quietly did the hard middle part is not. Both did real work. Only one is easy to recall.
This is why "just speak up more" does not help much. Talking in the wrong meeting changes nothing. Being in the right one changes almost everything.
Why fixing it afterwards backfires
After being passed over, most people try to correct the record. They send the message. They explain in the group chat. They bring it up in their next one on one.
The problem is timing. By then the story is already set, so you are asking someone to change their mind. That sounds like a complaint about status.
The exact same sentence, said a week earlier, would have sounded like a normal work update.
None of that is fair. It is just how it works.
What actually helps
Research on this points one way. People get credit through small, regular, ordinary updates while work is still happening. Not through arguing about it later.
A 2025 study of nearly a thousand managers found the same pattern from the other side of the desk. Given no record of a remote or hybrid employee's output, managers promoted and gave raises to the people they saw in person far more often, even when the work was identical. Handed an actual record of what someone did, that gap mostly closed. The record did the work that confidence was supposed to do.
In practice, that means saying what you are working on while you are still working on it. In the normal places where your team talks about work. In plain words, so someone could repeat it without you there.
It is one sentence, not a speech.
It also means being there, even for a few minutes, when a piece of work is being planned and named. That early conversation is where people decide whose project it is, usually without meaning to.
If you prefer to let finished work speak for itself, this can feel like bragging. It is not. You are just making yourself easy to remember. The other option is a colleague honestly describing what they knew about, which did not include you — not modesty.
Where to start this week
Pick the thing you are working on now that you would be annoyed to see credited to someone else. Then say one sentence about it, in the ordinary place your team talks about work, before it is finished.
Not a summary of your effort. A plain statement of what you are doing and what you are finding. "I am looking at why the vendor numbers keep moving, and I think it is the ramp assumption." That is the whole thing.
Do it once a week for a month on whatever you are currently working on. You are not building a case, you are making the connection between your name and the work ordinary enough that it forms without anyone deciding to.
If saying it in a group channel feels like too much, send it to your manager directly instead. That covers the person whose recollection matters most, and it is a much smaller thing to do.
The part that stays yours is tone. The same sentence reads as useful on one team and as a status claim on another, and that depends on things you can see and I cannot. What this gives you is the timing, which is the part most people get wrong.
If the sentence itself is what you are stuck on, that is worth working through properly rather than guessing at. There are ways to phrase an update so it carries your name without sounding like it is trying to.