Discussing performance ratings without demotivating employees takes more than good intentions. Here is a framework that keeps the conversation honest and useful.
Marketing Lead
April 10, 2026
•
6 Mins Read
The most technically well-designed performance review can destroy motivation in the delivery.
An employee who worked hard all year receives a "meets expectations" rating in a meeting that lasted 15 minutes, ended without a clear next step, and left them wondering if anything they did was actually seen.
That is not a rating problem. It is a conversation problem.
This article gives managers the structure and language to have a rating conversation that is honest and specific without deflating the people they depend on. It is particularly relevant to Nigerian, Kenyan, and Ghanaian workplace contexts where hierarchy, cultural communication norms, and limited HR infrastructure shape how these conversations land.
Most demotivating rating conversations share one or more of these failures:
This is a 45-60 minute structure. It works for all ratings: high, average, or below expectations. Adapt the language to the specific rating, but keep the structure.
Open by naming the purpose of the conversation and what comes after it.
"Today we are reviewing how this cycle went and agreeing on what comes next. I want this to feel like a real conversation, not a presentation of a form. I will share my assessment and the evidence behind it, and I want to hear your perspective too."
This opening matters in African workplace contexts where hierarchy can make employees feel they should receive the review passively without responding. Explicitly framing it as a two-way conversation gives them permission to engage.
Lead with specific, evidence-backed recognition. Not "you did a great job this year" but "the Q3 client migration project, you managed three stakeholders who had conflicting requirements and delivered on time without a single escalation. That was strong.
The specificity is what makes this land. Generic praise sounds like padding before the bad news. Specific praise signals that the manager actually watched the work.
State the rating clearly. Do not bury it or soften it to the point of confusion.
"Based on what I observed this cycle, I rated you as meeting expectations. I want to explain why."
Then provide two or three pieces of evidence that support the rating. Each should follow the SBI structure: Situation, Behaviour, Impact. What happened, what the employee did, what the result was.
Pause after explaining the evidence. Ask: "Does that feel like a fair reflection of the cycle? Is there anything I have missed or described incorrectly?"
This pause is crucial. It is not weakness. It is accuracy. If the employee has evidence that contradicts the manager's assessment, hearing it improves the rating's integrity and demonstrates that the manager is genuinely evaluating rather than judging.
Turn explicitly to what comes next. This is the part that most demotivating conversations skip entirely.
"Given where you are now, I want to talk about what next cycle could look like. The gap I see for you is X. Here is what I think it would take to move from where you are to where you want to be."
Name one capability to build, one stretch opportunity available, and one specific action the manager will take to support the development. Not three. One of each.
End with what the employee needs to leave knowing:
This is the conversation most managers in Africa avoid most successfully. They hedge, they soften, and they leave the employee unsure whether they received a serious feedback message or a mild suggestion.
A below-expectations rating delivered poorly does two kinds of damage: the employee feels personally attacked without understanding what to change, or the employee leaves without realising the severity of the message and makes no change at all.
Three principles for this conversation:
Pause. Do not push through the agenda. Acknowledge directly: "I can see this is hard to hear. Let us take a moment." Give the employee space to collect themselves. In many Nigerian and Kenyan workplace cultures, an employee showing emotion in a one-on-one is communicating something important about how the message landed. Treating it as a disruption to the agenda sends the wrong message entirely.
Sharing the rating in advance (the day before) gives the employee time to process before the conversation, which tends to produce better-quality discussion. It also prevents the shock response that makes the first ten minutes of the meeting unproductive. If your organisation does not have a norm around this, the manager sharing the rating and evidence in writing 24 hours before the meeting is a simple improvement that costs nothing.
First, listen fully before responding. Then test whether the disagreement is about evidence or about the standard. If the employee has evidence the manager missed, the rating should be reconsidered. If the disagreement is about the standard itself ("I think I should be rated higher because I worked hard"), the manager needs to explain the difference between effort and outcome and hold the rating.
A rating is a data point. The conversation is what turns it into something an employee can act on.
The managers who deliver ratings well are not necessarily the most skilled communicators. They are the ones who show up prepared, with specific evidence, a forward-looking plan, and the patience to listen before they conclude. That combination respects the employee's effort and gives the rating enough credibility to drive change.
