The week before a performance review cycle closes, HR starts receiving messages from managers asking for extensions, employees asking for clarifications about what they were supposed to deliver, and a few early disputes from employees who are already sure the rating they are about to receive is wrong.

Almost all of that chaos traces back to one failure that happened months earlier: expectations were not clearly set before the cycle began.

This article gives HR leaders and managers a practical guide to setting expectations before review season opens, including what to cover, when to do it, and how to handle the specific challenges of expectation-setting in Nigerian, Kenyan, and Ghanaian company environments.

What "setting expectations" actually means

Setting expectations before a review cycle means ensuring every employee has clear, documented answers to four questions:

1. What are my core responsibilities this cycle, and what does delivering them well look like?
2. What specific goals or OKRs am I being measured against, and how will progress be measured?
3. What is the rating scale, and what does each level mean for my role?
4. What behaviours or competencies am I expected to demonstrate, and what does "above standard" look like?

‍

An employee who can answer all four questions at the start of the cycle can predict their rating at the end of it with reasonable accuracy. An employee who cannot answer any of them will be surprised.

The expectation-setting conversation: a step-by-step guide

Step 1: Share role expectations first

Before discussing goals, share the role expectations document or competency framework. "This is what your role is expected to deliver at the standard we have set for this level. I want to make sure we are both clear on this before we set goals."

In African organisations where role descriptions are often sparse or outdated, this step may require the manager to articulate expectations that have never been formally written. That articulation is the most important investment the manager makes in the cycle.

Step 2: Set OKRs collaboratively

Do not hand OKRs down from above and ask the employee to sign. Collaborative goal-setting produces significantly higher commitment and significantly fewer end-of-cycle disputes about whether the goals were realistic.

A practical approach: the manager shares the team or department objectives, asks the employee to draft their own OKRs as a starting point, and then reviews and refines them together. This takes more time than a top-down assignment but produces goals the employee believes in.

Step 3: Define the rating standard explicitly

"Meeting expectations means consistently delivering against the role expectations and OKRs we have set. Here is what that looks like specifically for your role. Exceeding expectations requires doing that and demonstrably more. I want you to understand exactly what you are aiming for so you can make informed choices about how you prioritise your work."

This conversation is awkward for managers who are used to keeping rating standards vague. It is also the only version that is fair.

Step 4: Identify the behaviours and competencies that will be assessed

Share the competencies from the review form and explain what each means for this employee's role. A generic competency like "problem-solving" means different things for a software engineer and a sales manager. Be specific: "For your role, problem-solving means identifying process gaps before they escalate to leadership and bringing a proposed solution when you raise a concern."

Step 5: Document everything and share it with the employee

The goal of the expectation-setting conversation is a shared document that both parties can refer to throughout the cycle. It does not need to be long or formal. A brief email summary sent to the employee after the conversation is sufficient: "Following our discussion today, here is a summary of your role expectations, your Q3 OKRs, and the rating standard we discussed."

That email is the foundation of every subsequent check-in and the reference point for the review conversation at the end of the cycle.

Why expectation-setting fails in African organisations

• Role definitions are outdated or informal: the role the employee is actually doing is different from the role description. Fix: base expectations on current practice, not historical documentation
• Managers are reluctant to define the exceeds standard because they worry it creates a commitment they cannot fulfil. Fix: the exceeds standard is a description of a level of contribution, not a promise of what the rating will be
• Goal-setting happens as a formality: the employee fills in a goal template but neither party believes the goals are connected to what the company actually needs. Fix: cascade goals from department objectives so the connection is visible
• In cultures where hierarchy makes employees reluctant to ask clarifying questions, expectations that seem clear to the manager are not understood by the employee. Fix: after sharing expectations, ask the employee to describe in their own words what they understood, not "do you have any questions?"

Frequently asked questions

What if mid-cycle changes make the expectations set at the start of the cycle irrelevant?

Expectations set at the start of a cycle should be updated when the role or business context changes significantly. A 15-minute conversation to revise OKRs or update role expectations mid-cycle is much less costly than a review conversation at the end of the cycle where the employee is evaluated against goals the business abandoned in month two.

How do you set expectations for a new employee who is still learning the role?

New employees in their first 90 days should have differentiated expectations that focus on learning outcomes and early deliverables rather than full role performance. A useful framing: "In your first 90 days, success means understanding the role, building the key relationships, and delivering these three specific early outcomes. We will set performance expectations for the full role in month four once you have the foundation to be evaluated fairly against them."

The bottom line

Every performance review dispute, every rating surprise, and every "I did not know that was what was expected" moment can be traced back to the expectation-setting conversation that did not happen.

Setting expectations well takes about 45 minutes per employee at the start of each cycle. That investment prevents hours of dispute management, rating appeals, and loss of trust at the end of it. There is no performance review best practice that produces a higher return for the time invested.