How to Prepare for a Performance Review

Open your calendar, your sent mail, and your project tracker, and go back month by month. Write down everything you shipped, fixed, unblocked, or inherited in a mess. Do not filter yet — the point is to stop relying on memory, because the review always lands on the two months you can remember and the other ten disappear.

Rewrite each item so it answers 'so what'. 'Ran the onboarding sessions' becomes 'cut new-hire time-to-first-task from nine days to four'. Where you genuinely have no number, use a concrete before-and-after or a named thing that now exists because of you. A review panel can argue with adjectives; it is much harder to argue with a date and a count.

Ask two or three colleagues — including one you do not work with daily — for a single sentence you can quote: what changed because you were on the project. Do this two weeks ahead, not the night before. Written feedback from peers carries weight that self-assessment cannot, and it also surfaces problems while you still have time to mention them yourself.

Choose the two failures a fair reviewer would raise, and write what you would do differently with the benefit of hindsight. Naming them first removes their power to derail the meeting, and it demonstrates the one thing reviews are actually testing: whether you can look at your own work accurately. Do not pick fake weaknesses to look humble.

Ask your manager, in writing, whether this is a rating conversation, a development conversation, or a pay conversation — and whether they have already decided the outcome. The three require completely different preparation, and most disappointment comes from preparing for one and walking into another. If the rating is already fixed, your only real lever is the shape of the next six months.

Write the harshest fair criticism of your year, then write a two-line answer that neither agrees with everything nor denies everything. Something like: 'That is fair for the March release; what changed afterwards was X.' A prepared answer sounds like reflection. An unprepared one sounds like either defensiveness or collapse.

Decide what you want out of the meeting: a specific development opportunity, a change in scope, or a pay conversation — and prepare a fallback for each. Three ranked asks give the conversation somewhere to go when the first is impossible this quarter, and they make you look like someone planning a year rather than winning an argument.

Say the worst question and your answer aloud, twice. 'Why should you be rated above expectations?' is a different sentence in your mouth than in your head, and the first time you hear it should not be in the room. Practising also exposes answers that run past thirty seconds, which is roughly how long a manager listens before deciding.

Start with a single sentence that frames everything: 'Three things went well, one went badly, and here is what I want to change next year.' It gives the meeting a shape in ten seconds and stops the conversation from being a list of incidents in random order. Then let the evidence do the work.

When a criticism lands, ask what specifically prompted it and what 'good' would have looked like. Half the time the answer narrows the complaint to one incident; the rest of the time you learn the standard you were never told. Either way you leave with information instead of a verdict.

If you disagree with the rating, do not argue about the number — ask what evidence would have justified the higher one. Then ask whether that can be agreed in writing for the next cycle. Criteria you can point to later are worth more than a fight you win once, and managers find it much easier to concede a definition than a rating.

Send a short summary: what was agreed, what you will do in the next quarter, what you asked for, and what is still open with a date. Five lines, no editorialising. This is the document anyone will read when the next cycle starts, and it is the only part of the review that outlives the meeting.