The questions managers actually have about running performance reviews — answered directly for managers in African organisations.
Marketing Lead
.png)
June 2, 2026
•
5 Mins Read
Performance review season is when HR inboxes fill with questions managers did not know to ask six weeks ago. This article answers the most common questions before they become urgent, so managers can run better reviews and HR can spend less time in individual briefings.
"Meets expectations" means the employee consistently delivered against the defined role requirements and goals this cycle. "Exceeds expectations" means they did that and made a demonstrable contribution beyond what the role required. The key test for exceeds: can you name a specific thing the employee did that went beyond the role definition, and can you describe the impact? If yes, exceeds is defensible. If the employee simply did their job very well but within the role's scope, that is strong meets, not exceeds.
Rate the cycle, which is typically a quarter or a year depending on your cadence. If the employee had a strong first three quarters and a difficult final quarter, the full-cycle evidence suggests a meets or exceeds rating.
If the review is quarterly and it was a difficult quarter, it may appropriately rate below the employee's usual level. In either case, the narrative should note the context: this gives the employee a fair record and provides calibration with relevant information.
Before the review cycle ends, review your check-in notes, the employee's self-assessment, any 360 feedback collected, and the employee's documented goal progress.
If those sources do not give you enough to support a specific rating, the documentation gap is the problem. For this cycle, rate based on the best evidence you have and be transparent about the evidence limitations in the narrative. For the next cycle, commit to monthly check-in notes after every conversation.
Three preparations: have your evidence ready and organised before the meeting; share the rating in writing 24 hours before the meeting so the emotional processing happens before the conversation, not during it; and prepare the development plan before you go in so the meeting can end with a forward-looking action rather than just a difficult message.
Acknowledge the emotion when it appears. Do not rush through it. If the meeting becomes too difficult to continue productively, it is appropriate to pause and continue later in the week.
First, check whether the comparison is accurate: is the colleague doing genuinely comparable work at the same level? If yes, prepare your evidence for both ratings and be ready to explain the specific differences in output, quality, or competency that justify the different ratings. If you cannot explain the difference with specific evidence, the calibration process may have produced an inconsistency that HR needs to review.
Peer feedback and manager assessment measure different things. Peers rate how someone works with them: collaboration, communication, support. The manager rates the quality and quantity of the work output. High peer scores with low output scores are a common pattern and they are not contradictory. The employee may be an excellent team member who is not meeting the delivery standard. The development conversation addresses the output gap, not the peer relationship quality.
Do not rate competencies that you have no evidence for. If a competency is on the form but genuinely not applicable to the role, mark it as N/A and note why. Rating a competency you cannot observe on the basis of general impression is a bias source, not an evidence-based assessment. If the form is systematically non-applicable to your team's roles, raise that with HR as feedback for the next cycle's design.
Calibration notes are typically confidential to HR and management and are not shared with employees. The outcome of calibration (the final rating) is what the employee receives. If an employee asks why their rating changed after calibration, you can explain that the calibration process reviewed their rating against consistent standards and the adjustment was made to ensure fairness across the organisation, without sharing the specific content of the calibration discussion.
A rating adjustment based on leadership preference rather than performance evidence is a favouritism problem, not a calibration correction. If you are pressured to rate an employee lower because of political considerations rather than documented performance, that is a process integrity issue that HR needs to know about. Your responsibility as a manager is to assess performance accurately. HR's responsibility is to ensure the calibration process does not become a vehicle for political adjustments.
Specific enough that both parties know what success looks like. A development plan that says "improve communication skills" is too vague to be useful. A plan that says "lead the Q3 cross-departmental briefing and debrief with manager afterward" is specific enough. Include: the development goal, the specific action, the manager's support commitment, and a follow-up date within six weeks.
Follow through, or communicate proactively if circumstances change. "I committed to arranging X and I have not been able to. Here is why and here is what I can do instead by [revised date]." Development plan commitments that are silently abandoned are more damaging than commitments that are revised with communication. Employees who see managers not following through on development commitments learn quickly that development plans are theatre.
The questions managers ask about performance reviews are almost always the same questions. Answering them consistently, in advance, with specific and honest guidance, produces better review quality across the organisation than answering them individually under deadline pressure each cycle.
HR teams that publish a manager FAQ at the start of each review season, and update it with new questions each cycle, build a knowledge base that compounds over time and reduces the individual briefing burden that drains HR capacity during review season.
