HR-side mistakes in performance reviews are less visible than manager mistakes but just as damaging. Here are the most common ones and how to fix them.
Marketing Lead
May 2, 2026
•
4 Mins Read
When a performance review cycle fails, the instinct is to look at manager behaviour. The review was delivered poorly. The manager was biased. The feedback was vague.
Less often does the analysis turn to HR. But HR is the architect of the process, the trainer of the managers, and the keeper of the standards. When the process is poorly designed, when managers are trained inadequately, and when calibration is absent or perfunctory, the downstream damage is inevitable regardless of how skilled individual managers are.
This article covers the most common mistakes HR teams make in performance review cycles and the practical fixes for each.
Many African HR teams design the review cycle based on HR best practices from external sources, without significant input from the managers who will run it or the business leaders whose strategic priorities it should serve. The result is a technically sound process that serves nobody's actual needs.
The fix: before designing the next review cycle, interview five managers and two senior leaders. Ask: what do you need from this process? What does it currently produce that you cannot use? What decisions does it need to support? The answers will be more useful than any HR framework.
A one-hour manager training session at the start of a manager's tenure, with no reinforcement before each review cycle, produces little lasting change in review quality. By the time review season arrives, the training is forgotten and the manager defaults to their instincts.
The fix: run a focused 60-90 minute manager briefing before every review cycle. Cover the current cycle's rating scale definitions, the evidence requirement, and the calibration process. This is not repetitive: the context changes every cycle, and the briefing creates an accountability signal that review quality is being actively managed.
Calibration is the accountability mechanism that makes the entire review process credible. When HR runs calibration as a formality where ratings are presented but not challenged, the ratings that go to employees are the unreviewed products of individual manager bias.
The fix: calibration must include a challenge function. HR should identify the top 20% and bottom 20% of ratings across comparable roles and require managers to defend those outliers with specific examples. Ratings that cannot be defended should be reconsidered before they are finalised.
In many African companies, the performance rating scale is a set of labels with no agreed definition of what each level looks like in practice. "Exceeds expectations" means different things to different managers. The result is a rating distribution that reflects manager personality as much as employee performance.
The fix: before the cycle opens, HR publishes a one-page rating scale guide that defines each level with two or three observable behavioural examples for a typical role. This does not need to be a comprehensive competency framework. It needs to be specific enough that two different managers would reach the same conclusion about a typical performance situation.
HR often measures review cycle success by completion rate: 95% of forms submitted on time. But a completed form with vague ratings and no development plan is worse than a slightly late form with evidence-backed ratings and a real development conversation.
The fix: add a quality signal to completion rate reporting. Sample 20% of submitted reviews and assess whether they contain specific examples, a development goal, and ratings that are internally consistent. Report on quality alongside completion.
The performance review cycle ends when the forms are submitted. Development plans are agreed, goals are set, and then nothing happens until the next cycle. The review produced data that is never used.
The fix: 30 days after the cycle closes, HR sends each manager a two-question check-in: "Have you had a follow-up conversation with each direct report about their development goal? If not, when will you?" That prompt, sent consistently, transforms the review from a one-time event into the start of an ongoing development process.
The non-negotiables are: evidence requirement, rating scale definitions, and calibration. Within those constraints, managers have significant flexibility in how they run the review conversation and structure the development plan. Consistency in standards does not require uniformity in delivery.
First, understand the reason for the resistance. Common causes: the manager believes the process is a waste of time (address with data on its outcomes), the manager lacks confidence in their ability to rate fairly (address with training and calibration support), or the manager is managing a conflict with a direct report that the review will surface (address with HR involvement). Different causes require different responses.
%20(1).jpg)
%20(2).jpg)
%20(1).jpg)
