Few rituals in working life are as widely dreaded — and as widely done badly — as the performance review. Managers postpone them; employees brace for them; and too often the result is an awkward hour, a number on a form, and nothing that actually changes. Yet done well, a performance review is one of the most useful conversations a manager and an employee can have: a chance to recognise good work, address what is not working, and agree where to go next. This guide covers how to get the frequency, the feedback, the goals and the follow-through right — and which pitfalls to avoid.
What a performance review is
A performance review is a structured conversation between a manager and an employee about how the employee is doing, what they have achieved, and what to focus on next. At its best it does three things at once: it gives honest feedback, it recognises contribution, and it sets clear goals for the period ahead.
The word "review" is slightly misleading, because the most valuable version looks forward as much as back. Yes, you discuss what has happened — but the point is to improve what happens next. A review that only grades the past, like a school report, misses most of its value.
It is also worth being clear about what a review is not. It is not a substitute for day-to-day management, not the only time feedback should be given, and not a box-ticking exercise to satisfy HR. When it becomes any of those, people rightly start to resent it.
Getting the frequency right
The single biggest mistake organisations make is relying on one big annual review and nothing in between. Twelve months is far too long to wait to tell someone they are off track, or to recognise that they are excelling.
A much healthier rhythm pairs occasional formal reviews with frequent informal check-ins:

- Regular one-to-ones — monthly or even fortnightly short conversations about how things are going, what is in the way, and what support is needed.
- Quarterly check-ins — a slightly fuller look at progress against goals, with time to adjust.
- A formal review once or twice a year — a more structured conversation that pulls the threads together and looks ahead.
The golden rule: nothing in a formal review should ever be a surprise. If an employee is hearing about a serious problem for the first time at their annual review, their manager has not been managing — they have been saving up bad news, which is unfair and ineffective. Frequent contact means issues get handled while they are small.
A good one-to-one every few weeks does more for performance than the best annual review ever could. The review should confirm what both people already know, not reveal it.
Giving feedback people can use
Feedback is the heart of a review, and the quality of feedback determines whether anything improves. Useful feedback has a few consistent features.
Be specific. Vague comments — "be more proactive", "you're disorganised", "great job" — give people nothing to act on. Concrete observations do: "When you flagged the supplier risk early last month, it saved us a real problem" or "The last three reports were late, which held up the rest of the team."
Focus on behaviour and impact, not personality. Describe what someone did and what effect it had, rather than labelling who they are. "You interrupted colleagues in the planning meeting" is fixable; "you're arrogant" is an attack.
Balance recognition and improvement. People need to hear what is going well, not only what is wrong. Genuine, specific recognition builds the trust that makes critical feedback land. A review that is all criticism demoralises; one that is all praise fails to develop.
Make it a conversation, not a monologue. Ask for the employee's own view, listen to it, and treat the review as two-way. People support conclusions they helped reach, and the employee often has context the manager lacks.
Point forward. End every piece of feedback with what to do next. The purpose is improvement, not judgement.
Setting goals that work
A review without clear goals for the period ahead is half a conversation. Good goals turn feedback into direction. The well-known principle is to make them specific and measurable, with a sensible timeframe — but two things matter just as much.
First, connect individual goals to the bigger picture. People are more motivated when they can see how their objectives support the team's and the organisation's aims. Linking personal goals to the team's key performance indicators or wider objectives gives work meaning and direction.
Second, agree goals together rather than imposing them. A goal someone has shaped is a goal they own. Discuss what is realistic, what support is needed, and how progress will be tracked, then write it down so both of you remember it.
A simple structure for each goal:
- What — the outcome you want, stated clearly.
- How measured — how you will both know it has been achieved.
- By when — a realistic deadline or review point.
- Support needed — what the manager or organisation will provide.
Goals set this way become the agenda for the next round of check-ins, which keeps the whole cycle connected instead of letting good intentions fade after the meeting.
Common pitfalls to avoid
Even well-meaning reviews go wrong in predictable ways. Watch for these:
| Pitfall | Why it harms | Better approach |
|---|---|---|
| Recency bias | Judging the whole period by the last few weeks | Keep notes through the year so the picture is fair |
| One-way monologue | The employee disengages and learns little | Ask questions and genuinely listen |
| Vague ratings | Numbers without meaning frustrate everyone | Tie any rating to specific examples |
| Surprise bad news | Feels unfair and damages trust | Address issues as they happen, all year |
| No follow-up | Goals are forgotten and nothing changes | Revisit goals in regular check-ins |
The pitfall that undermines everything is no follow-through. A review that produces agreed goals and then sits in a drawer until next year teaches people that the whole exercise is theatre. Follow-up — revisiting goals in your regular one-to-ones — is what makes a review matter.
It also helps to keep development feedback distinct from pay decisions where you can. Mixing "here's how to grow" with "here's your raise (or not)" in one conversation tends to make people defensive and stop listening. Strong people processes here reinforce other good habits, from sensible onboarding of new staff to building the kind of stable team that makes managing cash flow easier because you are not constantly rehiring.
The bottom line
A performance review done right is not an annual ordeal but the formal point in a year-round conversation. Review often through regular check-ins so nothing comes as a shock; give feedback that is specific, balanced and focused on behaviour and impact; set clear, measurable goals together and connect them to the bigger picture; and — above all — follow through. Get this right and reviews stop being something everyone dreads and become what they should be: the engine of people getting better at their jobs and feeling valued for it.
Frequently asked questions
How often should performance reviews happen?
More often than once a year. A formal review once or twice annually works far better when supported by regular, lightweight check-ins — monthly or quarterly one-to-ones. Frequent contact means issues are addressed while they are small and nothing in the formal review is a surprise.
What makes feedback actually useful?
Specificity and a focus on behaviour rather than personality. 'You missed the last three deadlines, which delayed the team' is actionable; 'you're disorganised' is not. Balance recognition of what is going well with clear, concrete areas to improve, and always point toward what to do next.
Should performance reviews be linked to pay?
They can be, but mixing development feedback with a pay decision in the same conversation often makes people defensive and less open to learning. Many organisations separate the developmental review from the pay discussion so each can be honest. There is no single right answer — be clear about which conversation you are having.
How do I handle a review when performance is poor?
Be honest, specific and fair, focus on behaviours and outcomes rather than the person, and agree clear, achievable steps with a timeframe and support. Document what was discussed. For formal capability or disciplinary processes, follow a fair procedure — Acas provides guidance on doing this properly.
Join in — free. Comments on Daily Junction are for members, so real names stay rare and bots stay out.
One field. We email you a 6-digit code — no password needed. Your comment is kept while you do it.
Under 13? You’ll need a parent’s OK first — it takes them one click.