How to Conduct Performance Reviews That Actually Improve Performance
Performance reviews have a bad reputation. Employees dread them, managers rush through them, and nine times out of ten, they end in awkward silence where nothing actually changes. But here is the thing: when you know how to conduct performance reviews that actually improve performance, they become one of the most valuable tools in your management kit. Not a box-ticking exercise. Not a once-a-year grind. A structured opportunity to recognise good work, address problems, align expectations, and plan development.
This guide explains how to make performance reviews work — drawing on CIPD research on well-being at work and ACAS guidance on disciplinary and grievance procedures. If you're running a small business without a dedicated HR team, this is even more critical — your reviews are probably the only formal feedback your staff get, so they need to count.
Why most performance reviews fail
Here's what goes wrong — and why it's not actually your fault. The system is broken before you even sit down:
They happen too infrequently. An annual review means feedback is three, four, or six months old by the time it's delivered. The employee can't remember the context. You can't remember the details. By then, the behaviour you wanted to address either got worse or they've assumed you didn't care.
They are vague to the point of uselessness. "Good job this year" and "needs to improve communication" sound professional but they're meaningless. The employee leaves thinking "okay, but what do I actually do differently?" and you leave wondering why nothing changes.
They are one-directional. The manager talks, the employee listens (or pretends to). There's no genuine conversation. This isn't a review — it's a verdict. And nobody takes a verdict they had no part in.
There is zero follow-through. Goals are set on a Tuesday afternoon. They're forgotten by Friday. By the time the next review rolls around, you're both wondering what happened.
They're tied to pay. The moment salary enters the room, the conversation stops being about development and starts being a negotiation. The employee stops being honest. You stop being candid. Everyone leaves unsatisfied.
A better approach: The four non-negotiables
Frequency matters more than formality
Run formal reviews at least twice a year. Quarterly is better if you can manage it. Supplement those with informal check-ins every two to four weeks — a five-minute chat, not a meeting. Regular feedback eliminates the shock factor that makes annual reviews so uncomfortable. Your staff know where they stand. You know what's working and what isn't.
Separate performance from pay
If you can, hold the performance conversation in one meeting and the salary conversation in another. Different day, different room, different framing. When employees know their pay review is coming separately, they're more likely to be honest about challenges and development needs. This is CIPD best practice, and it actually works.
Make it a genuine two-way conversation
A review should be a dialogue, not a lecture. The employee should talk at least as much as you do. Ask questions. Listen to the answers. Be willing to learn something. If you're doing 80% of the talking, you're doing it wrong.
Build in accountability for yourself
You're the manager. You set the tone, you do the prep, and you follow through. If you promised training, provide it. If you said you'd adjust their responsibilities, do it. Nothing undermines a review process faster than a manager who doesn't follow through on their own commitments.
Preparing for the review
As the manager
Review the evidence. Look at the goals you set in the last review. What was achieved? What wasn't? Why? Review any notes from regular check-ins. Pull together specific examples of good performance and areas for improvement. If relevant, gather feedback from colleagues who work with this person (with their permission — don't do surprise feedback).
Plan the conversation. Identify the two to three most important points to discuss. Not ten. Two or three. Prepare specific examples for each one. Think about development opportunities and how this role fits into their longer-term career. What are they actually good at? What are they trying to learn?
As the employee
Give them time to prepare too. Send a self-assessment form or reflection questions a week before the review:
- What are you most proud of since the last review?
- Which goals did you hit? Which ones did you miss, and why?
- What challenges got in your way?
- What support do you actually need?
- What would you like to focus on next?
An employee who has reflected on their own performance before the meeting will contribute more meaningfully. You'll have a conversation, not a monologue.
The review conversation — a structure that works
A good review follows a consistent shape:
1. Set the tone (5 minutes). Start positively. Explain the purpose clearly: "This is a conversation about how things are going, what's working well, and what we can improve together. I want to hear your perspective too. This is not a surprise verdict — it's a discussion."
2. Review the period (15–20 minutes). Walk through the goals from the last review. What was achieved? Acknowledge successes with specific examples. "Your handling of the client complaint last month was excellent — you identified the root cause, resolved it quickly, and they specifically thanked us" lands differently than "good job." What wasn't achieved? Understand the reasons without blame. What unexpected contributions did they make?
3. Feedback (10–15 minutes). Here's where most managers either go soft or go harsh. Don't do either.
For positive feedback: Be specific about what was good and why it mattered. Use the SBI model: Situation, Behaviour, Impact. "During the product launch, you coordinated between sales and marketing without being asked, which meant the launch materials were ready a week early and the sales team felt prepared." That's three times more useful than "great initiative."
For improvement areas: Focus on behaviour and outcomes, not personality. "Project updates are often submitted a few days late, which delays the team's planning — what can we do to address this?" opens a conversation. "You're disorganised" slams the door shut. Always use the same SBI structure so feedback doesn't sound personal.
4. Development discussion (10 minutes). What skills do they want to develop? Are there training opportunities or stretch assignments? How does this role fit into their longer-term plans? What support do they need from you?
5. Set goals (10 minutes). Agree on three to five goals for the next period. More than that and focus dissolves. Good goals are specific enough that both of you know what success looks like. You can measure them. They're challenging but realistic. They connect to the team's objectives and their development. And they have a deadline.
6. Summarise (5 minutes). Recap the key points, agreed goals, and actions. Confirm when you'll check in next. Both of you should leave with the same understanding of what was discussed and what happens next.
After the review: The part most people skip
Document it. Write a brief summary: key points discussed, goals agreed, any actions for either party. Share it with the employee so you both have the same record. This matters more than it sounds. Store it in your HR system or payroll software alongside their other records. This creates a history of performance conversations that's invaluable for future reviews, promotions, or — if necessary — performance management.
Follow through. If you promised training, arrange it. If you said you'd make a change, make it. This is non-negotiable.
Continue with regular check-ins. The review is not the end. It's a checkpoint. Keep having informal conversations to track progress on goals, provide ongoing feedback, and address issues as they come up. This is what prevents surprises at the next formal review.
Common traps to avoid
Recency bias. Focusing only on the last few weeks instead of the entire period. Counter this by reviewing evidence and notes from the full review period before you sit down.
Avoiding difficult conversations. If you have concerns about performance, the review is where you raise them — clearly and constructively. Avoiding the issue does them a disservice and lets problems grow.
Rating inflation. Giving everyone a top rating to avoid conflict makes the review meaningless. Be honest. Differentiate between good, adequate, and below-standard performance.
Making it a monologue. If the employee sits in silence while you deliver a speech, it's not a review — it's a verdict. Create space for them to share their perspective, challenges, and ideas.
Making it personal. Feedback should address behaviour and outcomes, not personality. "Your reports have contained several errors recently" is actionable. "You're careless" is not.
How to do this without an HR department
You don't need a complicated system. Start with:
- A simple template for the review conversation (reuse it every time)
- A shared document for goals and follow-up notes
- Calendar reminders for reviews and check-ins (it's easy to forget)
- A commitment to doing it consistently, even when you're busy
If you're using HR software for small businesses, you can store review records alongside employee profiles, payroll data, and probation notes in one place. But honestly, the most important tool is a manager who takes the time to prepare, listen, and follow through.
One more thing: if you're onboarding new employees, start the feedback habit from day one. Don't wait until the formal review. Check in regularly. Make it normal. By the time the formal review happens, there will be no surprises on either side.
Frequently Asked Questions
Q: How often should we conduct performance reviews?
A: At least twice a year formally. Quarterly is better. The gap between formal reviews should be filled with regular informal check-ins every two to four weeks. Annual reviews only are too infrequent — feedback becomes stale and problems get worse before you address them.
Q: Should performance reviews be linked to pay?
A: No, ideally not. When pay is on the table, the conversation becomes a negotiation instead of a genuine discussion about performance and development. If you must link them, do the performance review first, then have a separate conversation about pay at least a week later.
Q: What if I'm reviewing someone I don't like?
A: Stick to behaviour and outcomes. Don't rely on personality judgments. Focus on specific examples: "The project deadline was missed by three days" instead of "You're unreliable." If you're struggling to find any positives, that's worth examining — but the review isn't the place to sort out your personal conflict. Separate that conversation from the performance review.
Q: How do I handle a review if someone is about to be let go?
A: This is where proper documentation matters. If performance has been an issue, you should have been addressing it in regular check-ins and check-in notes long before the formal review. If you're moving toward disciplinary procedures, that's a different process with its own rules. Don't use the performance review to surprise someone with bad news they should have seen coming.
Q: Can we skip the formal review if we have regular check-ins?
A: No. Check-ins are essential, but they're not a substitute for a formal review. The formal review is a chance to step back, reflect on the whole period, set new goals, and create a documented record. It's different in tone and purpose.
Q: What if an employee disagrees with their review?
A: Listen to their perspective. If they have a valid point, adjust your feedback. If you disagree, explain why clearly. Document their disagreement in the review summary if they want it recorded. This is why two-way conversation during the review matters — disagreements should surface during the conversation, not after.
Q: How do I prepare if I haven't been doing regular check-ins?
A: Gather evidence from the full period: emails, project outcomes, feedback from colleagues, and your own notes. Be fair about what you can actually assess. Acknowledge to yourself where you've dropped the ball on regular feedback, and commit to doing better going forward. Use this review as a reset point.
Q: Should performance reviews be different for someone in their probation period?
A: Yes. Probation reviews are more frequent, more focused on whether they fit the role, and have a different purpose — confirming the hire or addressing performance issues. After probation, your review process changes to focus on development and contribution.
The bottom line
Performance reviews work when they're specific, regular, genuinely two-directional, and followed by action. They fail when they're vague, infrequent, one-sided, and forgotten by Wednesday. The difference isn't a complicated system or expensive software. It's a manager who takes the time to prepare, listen, and follow through.
Start now. Pick a date for the next round of reviews. Set a calendar reminder for the one after that. Prepare one template and reuse it. That's enough to begin. When your staff know what to expect, when they have regular feedback, and when you actually do what you say you'll do, performance reviews stop being something people dread and start being something that genuinely improves how your business works.