How to prepare for a performance review
A practical guide
Most people prepare for a review the same way: a stressful evening scrolling back through email, chat threads, and old tickets, trying to remember what they did all year. It's slow, it's anxiety-inducing, and it systematically undersells you — because you only recover the work you happen to stumble across.
Here's a calmer way.
1. Beat recency bias first
The single biggest problem in reviews is recency bias — recent events crowd out the whole period. Your manager has it about you; you have it about yourself. So don't start from memory. Start from a record: your calendar, shipped work, and anything you logged along the way. If you kept a brag document, this step is already done.
2. Gather evidence, grouped by theme
Pull your accomplishments into a few buckets — delivery, collaboration and influence, craft, growth. For each item, capture the impact, not just the activity: what changed because you did it.
3. Frame wins as stories
The most persuasive format is STAR — Situation, Task, Action, Result. It forces you to state the outcome, which is the part reviewers actually weigh.
4. Write the draft, then edit
Don't write from a blank page. Assemble the evidence, dump it into your review's structure, then edit for tone. Editing is fast; excavating is slow. If you're unsure what a strong finished draft looks like, start from these self-review examples.
5. Write for the room you won't be in
At most companies your rating isn't decided in your 1:1 — it's decided in a calibration meeting where your manager defends you to people who've never seen your work. Your self-review is their ammunition. Give them lines they can read aloud: short, specific, with the result attached. A vague paragraph helps nobody argue for you; "cleared a six-week backlog and unblocked the launch" survives being quoted.
6. Keep it going for next time
The only real fix is to not cram at all — to have the record ready before review season starts.
If your review is two weeks away
Working backwards from the deadline:
- Two weeks out — one hour of excavation: calendar, sent folder, closed tickets, old status updates. Dump everything into one doc, ugly is fine.
- One week out — sort the dump into themes and rewrite each item as impact ("what changed because I did it"). Cut anything you can't finish the sentence for.
- Two days out — draft in your review's actual format, then read it aloud once. The bullets that make you cringe are activities, not impact; fix or cut those.
Do it without the cramming
Nisshi removes steps 1–4 entirely. You log a few lines about your work as you go; it generates weekly and sprint summaries automatically, turns them into STAR stories, and drafts a full self-review for any date range on demand. Come review time, you're editing a draft built from real evidence — not reconstructing a year from memory. It all runs on your Mac, privately.