Review season rewards people who can produce evidence, not people who work hardest, and evidence takes weeks to assemble. This order moves from other people's words to your own judgment to numbers to capability to leverage, then ends with a comparison that only works once the first five exist. Collect before you need it, because memory is a poor witness under pressure.
Step 1: Collect what other people already said
Start with material you don't have to generate. Praise and feedback already exist somewhere — a Slack reply, a client email, a line in a retro doc — and grabbing these first gives every later step something dated and external to lean on instead of your own recollection. Copy each one into a single folder or note called Evidence, and keep the surrounding context: the date, who said it, what the project was. A line like "this turnaround was fast" means nothing in eight months without the thread wrapped around it. The usual failure here is mental noting — reading a warm message, feeling good, closing the tab. Screenshot or forward it within the hour, and park it in a personal archive rather than a work inbox you lose access to when you change roles.
Step 2: Capture a problem that used to stall you
Where step 1 collected other people's words, this one asks for your own judgment. Pick a problem you solved in the last six months that would have stopped you a year ago — not something impressive on paper, something that genuinely used to be slow or confusing. Write three lines: what the problem was, what specifically made it hard then, and what you did differently this time. A useful example: a monthly reconciliation that used to eat a full day of manual cross-checking, now handled by a query you wrote and a two-item checklist you follow. People tend to reach for company-scale problems at this stage, which nobody can verify and you will forget the details of. Keep it small enough to explain in ninety seconds.
Step 3: Attach a number to your work
Numbers are the item most people skip, and by now you have enough narrative to make one land. If a clean metric exists, use it. If it doesn't, build an honest proxy: hours saved per week multiplied by weeks, error rate before and after, tickets closed per sprint, pages shipped. Write the baseline beside the result so the change is visible — "onboarding questions from roughly ten a week down to two" beats "improved onboarding" every time. Stay conservative, because a number a manager can sanity-check is worth more than a large one they doubt. Expect the reviewer's first question to be who else contributed. Name the teammates involved and your specific part, so the claim holds up rather than folding the moment someone asks.
Step 4: Prove a skill needs less help
Shift from outcomes to capability. Skills are the hardest thing to notice in yourself, because the moment you get good at something it stops registering as a skill at all. Name it precisely, then write a before-and-after. Weak version: "better with data." Strong version: "in January a senior engineer rewrote every query I wrote; now I write and tune them myself and only ask when a query plan looks off." Add the evidence that less help is actually happening — fewer review comments on your pull requests, fewer questions in the shared channel, someone pinging you instead of the other way round. The trap is choosing something vague like communication or leadership, which nobody can verify and you will struggle to defend out loud. Pick a skill you can point at an artifact for.
Step 5: Show how you made someone else faster
Help you gave other people is the strongest and most neglected item on this list, since seniority is measured in leverage rather than personal output. Describe one concrete instance: who you helped, what you did — paired on a tricky bug, wrote the runbook they now follow, reviewed their design doc before it went out — and what changed for them afterward. The outcome detail carries the weight: their on-call shift got quieter, they shipped the feature without escalating, they started clearing that class of ticket alone. Frame it as teaching rather than rescue. "I fixed their broken migration" reads as you taking over; "I walked them through the migration and they ran the next one solo" reads as you building capacity. If you can, ask them what they'd say changed.
Step 6: Write the six-month comparison
This goes last because it needs the previous five items as raw material. Write one paragraph, five or six sentences, comparing how you work now to six months ago, and make every claim a behavior rather than a feeling. Sketch two short columns first, then versus now. "Six months ago I waited to be told priorities; now I bring a proposed order to the Monday sync." "Six months ago I escalated ambiguous tickets; now I resolve most and flag only the ones with a real deadline at risk." Words like confident or proactive get deleted unless a behavior sits directly beside them. The common misstep is turning this into a feelings diary or a brag sheet. Stick to what you did, when, and what changed as a result of it.
A reminder in a phone app disappears the instant you dismiss it and leaves nothing behind. Six lines on a paper strip taped inside a desk drawer get visibly shorter as you cut them off, and the strip stays until the last one is gone. Start collecting a month before review season, not the week of.