Most people treat a performance review as something that happens to them. The ones who get ahead treat it as a meeting they prepare for — with evidence, a narrative, and clear goals.
Build your evidence
- List your wins — projects delivered, results, problems solved, with numbers where you can.
- Note where you grew or took on more than your role.
- Gather any positive feedback you received during the period.
Own the story
Don't wait to be assessed — arrive able to summarise your year in a few clear points. If there were setbacks, name them yourself with what you learned; it reads as maturity, not weakness.
Bring your own agenda
- What you want next — growth, responsibility, a raise, a new direction.
- Questions about how you can progress and what “great” looks like.
- If a raise is the goal, prepare that case too — see how to ask for a raise.
After the review
Get any agreed goals and development points in writing, and set your own check-in dates. That's how a review turns into actual progress.
Rehearse the awkward bits out loud
Most people prepare their achievements and stop there. The parts that actually decide how the meeting goes are the ones you'd rather skip: the pay conversation, the project that went sideways, the feedback you disagree with. If the first time you say those words is in the room, you'll fumble them. Say them out loud beforehand — to a mirror, a partner, or a voice note played back.
- The ask. Practise saying the exact sentence: "Based on X and Y, I'd like us to talk about a raise to [figure]" or "I want to move toward [role]." Vague hopes get vague answers.
- The stumble. Have a two-sentence version of anything that went wrong: what happened, what you changed. Own it before they raise it and it stops being ammunition.
- The pushback. If you disagree with something, rehearse a calm "Can you give me a specific example?" rather than getting defensive on the spot.
Time it right
Ten minutes of saying it aloud beats an hour of silently re-reading notes. Your mouth needs the reps, not just your eyes.
When it goes badly — surprise criticism
Sometimes you walk in prepared and still get blindsided by criticism you didn't see coming. The instinct is to argue or shut down. Do neither. The move is to slow the moment down and get specifics, because vague criticism can't be acted on and shouldn't be accepted at face value.
- Don't respond to the headline. "You're not a team player" is an opinion, not evidence. Ask: "What's a specific moment that gave you that impression?"
- Buy time if you need it. It's completely fine to say "I want to think about that properly — can we come back to it?" You don't have to have the perfect answer in ten seconds.
- Separate the true bit from the unfair bit. There's often a grain of truth wrapped in bad delivery. Take the grain, park the rest.
- Get it in writing after. Follow up with a short email summarising what was raised and what you agreed to do. It protects you and shows you took it seriously.
How to know it actually worked
A review that felt pleasant but changed nothing was a waste of both your time. A good one leaves you with something concrete you can point to in three months. Before you leave the room, make sure you can answer: what specifically do I need to do differently, and what happens if I do it? If the whole thing was warm words and no next steps, you didn't get a review — you got a chat. Send a follow-up email that same week listing the goals, the timeline, and anything they committed to on their side, so both of you are working from the same page rather than two fading memories.