Why tracking your wins feels wrong — and why you need to do it anyway

Every time you don't write down what you did, you're betting on someone else's memory. That's the bet. And memory is a terrible bet.

The instinct to stay quiet about your work often feels like humility. It isn't. It's a form of magical thinking that assumes your manager is paying close enough attention to remember what you did six months from now. They're not, not because they're careless, but because that's not how memory works.

Why your manager can't remember what you did

Picture your manager's Tuesday. Back-to-back meetings. Four different Slack threads. They catch something good you did, a sharp call in a design review or a fix that prevented an outage. They register it, nod, and move on. Their brain files it in short-term memory.

Then the day continues. A hard conversation at noon. An escalation from another team at 3pm. The commute home, an errand they forgot. By Wednesday morning, parts of what they observed the day before have faded. Not because you're unimportant. Because that's what brains do with unreinforced information.

The science behind the forgetting

Hermann Ebbinghaus documented this in 1885. In his foundational research (Memory: A Contribution to Experimental Psychology), he showed that without reinforcement, people forget roughly 70% of new information within 24 hours, and retention drops below 20% after 30 days. Nothing about human memory has changed since. Your manager is subject to the same curve as everyone else.

How recency bias erases your Q1

Even if your manager remembers something from earlier in the year, it won't feel as vivid as what happened last week. This is recency bias — the brain's tendency to overweight recent events when forming judgments. Daniel Kahneman covers it in Thinking, Fast and Slow (2011): the availability heuristic means that easier-to-recall events carry more weight in assessments than older, harder-to-surface ones.

The practical effect: a slow Q3 can overshadow a strong Q1 when review season arrives. The work doesn't change. The weight it carries in someone's memory does.

Most engineers don't account for this. They work hard all year, deliver real things, and arrive at review time with nothing to show except a general sense that they did good work. That sense doesn't travel. It won't survive a calibration meeting where other managers are asking pointed questions about specific contributions. Your manager needs to be able to name things. Memory alone won't get them there.

Documentation is information management, not bragging

There's a real distinction between self-promotion that feels like bragging and documentation that functions as a record. Standing up in a team meeting to announce how great you are is self-promotion. Keeping a running log of your impact, shared quietly with your manager, is something different. It's information management.

Your manager goes into calibration with other managers. They need to advocate for you. To advocate effectively, they need material: specific contributions, concrete outcomes, things they can name in the room. If you haven't given them that material, they're working from memory, which is unreliable by design.

You're not being humble when you stay quiet. You're leaving your advocate without evidence. Documenting your work is how you transfer that evidence to the person who needs it at the moment it matters.

What to actually do

Open a document. Call it anything: wins, notes, brag doc, work log. Write down three things you did in the last two weeks that had real impact. Not your whole job description, not every ticket you touched. Specific things with specific outcomes.

A sentence each is enough:

"Fixed the auth bug causing 3% of mobile logins to fail, deployed last Thursday."

"Proposed the schema change in the API review that cut query time by 40%."

Do this now, then do it again next week. After a month, you have a document that doesn't depend on anyone's memory.

The weekly note

Some engineers send a version of this to their manager weekly. If you haven't tried that, the weekly update is one of the most useful habits you can build. Five minutes, and your manager gets something concrete to reference at review time. The companion lesson The Weekly Update walks through how to structure one that actually gets read.

The key is to capture things while they're fresh. The fix you shipped two weeks ago feels obvious now. In eight months, you won't be able to reconstruct the context, and neither will anyone else. Write it down while you still can.

What it looks like in practice

Take an engineer — call her Jordan. Every Friday afternoon, she sends her manager a short note. Three bullets. Takes about five minutes. She doesn't treat it as reporting up; she treats it as keeping a shared record.

Six months later, at year-end calibration, her manager doesn't have to reconstruct the year from fading impressions. They pull up the notes. Specific examples, dates, outcomes. They can advocate with evidence, not a vague sense of "she did good work."

Jordan's colleague did work that was just as strong. But he never documented it, never sent the notes, never built a record. At calibration, his manager shrugged. Nothing to pull up.

The difference between those two outcomes wasn't performance. It was evidence.

Key takeaways

• Your manager forgets most of what they observe within 24 hours. Ebbinghaus's forgetting curve applies to everyone, including the people evaluating your work.
• Recency bias means contributions from earlier in the year get systematically underweighted at review time unless they're documented.
• Documenting your wins isn't self-promotion. It's creating material your manager needs to advocate for you when it counts.