Performance Review Prep: How to Document Your Year as It Happens
Most people prepare for performance reviews by reconstructing 6-12 months from memory. The result is predictable: you undersell yourself. A small weekly habit fixes this.
Performance review season has a ritual. Two weeks before the self-assessment is due, you open a blank document and stare at it. You check your calendar. You skim old Slack messages. You try to remember what you did in March. March is a blur. Most months are a blur.
So you write about the last 6-8 weeks, because that's what you actually remember. You pad it with phrases like "contributed to cross-functional initiatives" and "drove alignment across teams." Your manager reads it, nods, and bases the review on what they remember, which is also mostly the last two months.
You both know this isn't a great representation of your year. Neither of you does anything about it.
The recency problem
There's a name for this: recency bias. People overweight recent events when evaluating a longer period. Your manager does it when writing your review. You do it when writing your self-assessment. The result is that Q1 and Q2 basically don't exist unless something went spectacularly right or wrong.
This is how a developer who shipped a major feature in February but had a quiet November ends up with a "meets expectations" rating. The feature mattered. But by December, the memory has lost its edges. The specifics -- how many users it affected, what problem it solved, what constraints you worked around -- are gone. What's left is a vague sense that the year was "fine."
The opposite happens too. If your last two months were rough -- a project hit unexpected delays, a team reorg threw things off -- that colors the entire review, even if the first ten months were strong.
What to capture (it's not just wins)
Most advice about review prep says "track your wins." That's incomplete. Performance reviews cover more ground than a highlight reel. Here's what's worth writing down each week:
Accomplishments with context. Not just "shipped the feature" but what it took. The timeline, the constraints, who you worked with, what the outcome was. "Led the migration of 3 services to the new API over 6 weeks, coordinating with the platform team and reducing response times by 35%" is a self-assessment sentence that writes itself. You won't reconstruct those details in December.
Challenges you navigated. The project that almost derailed but didn't. The stakeholder conflict you resolved. The technical decision where you had to weigh competing priorities. These demonstrate judgment, and judgment is what separates "meets expectations" from "exceeds." Write them down while the details are still sharp.
Feedback you received. Positive feedback from a manager, a peer, a client. Also constructive feedback you acted on. Both tell a growth story. If your manager said in April that your technical presentations were improving, that's evidence of development. If a peer thanked you for helping them debug a production issue, that's evidence of collaboration. These things evaporate from memory fast.
Scope changes. Your role probably shifted during the year. Maybe you took on a new project mid-cycle, mentored a junior teammate, or stepped in when someone left the team. These are contributions that often get overlooked in reviews because they weren't in the original plan. If you don't write them down, you won't think to mention them.
Things you learned. New tools, new domains, new approaches. This category matters more than people think. Showing that you actively developed your skills over the year signals investment in the role. It also gives you material for the "growth areas" section of the review, which most people fill in with vague aspirations instead of specific evidence.
The Friday habit
This takes about 2-3 minutes. Friday afternoon, before you wrap up for the week. Answer one question: what happened this week that I'd want to remember at review time?
That's it. You're not writing polished prose. You're writing notes to your future self. A few sentences per week is plenty.
Here's what a typical entry looks like:
Finished the dashboard redesign ahead of schedule. Product team said it reduced support tickets about the reporting page by about 40% in the first week. Also had that conversation with Priya about the data pipeline priorities -- she agreed to push the less critical migration to Q3 so we could focus on the real-time features. Feedback from standup: James mentioned my RFC on the caching strategy was the clearest technical doc he'd read from our team.
Four sentences. A minute and a half of writing. But in November, this entry gives you an accomplishment with a specific metric, a prioritization decision with a named outcome, and a piece of peer feedback. That's a paragraph of your self-assessment, done.
Why this changes the review conversation
When you sit down to write your self-assessment with 40+ weeks of notes, the experience is different. Instead of trying to remember what happened, you're selecting from a record. You're choosing which stories to highlight, not scrambling to find any stories at all.
The psychological shift matters too. When you can see the full year laid out, you stop underselling yourself. Most people are surprised by how much they actually did. The weeks blend together in memory, but on paper, the pattern of consistent delivery and growth is clear.
It also changes the conversation with your manager. Instead of "I think I did well this year" (which puts the burden on them to agree or disagree with a feeling), you can say "Here are the specific things I delivered, with outcomes." That's a different kind of conversation. It's grounded in evidence, and evidence is harder to discount than impressions.
It's Q4 -- start now anyway
If you're reading this during review season, it's not too late to reconstruct some of the year. Check your project management tools, old PRs, sent emails, and calendar entries. You'll recover more than you think.
But next year, do yourself a favor. Start the weekly habit in January. Five minutes a week saves you the December scramble and gives you a better review. The math is simple: about 3 hours of writing across the year, spread in 2-minute chunks you barely notice, versus one stressful weekend trying to reassemble 12 months from fragments.
If you want a structured format for the weekly entries, the three-question template is a good starting point. You can do it in a text file, a notes app, or in Koru, which organizes your entries and helps you surface patterns when review time comes.
Either way, stop relying on memory. It's not on your side.