Employees cannot aim for good performance if nobody has defined what it looks like. Here is how to set the standard — and communicate it — in African organisations.
Marketing Lead
May 8, 2026
•
4 Mins Read
"Meets expectations" is the most common rating in most performance review systems. It is also the least defined.
Ask ten managers what "meets expectations" means for a software engineer, a sales executive, and a finance analyst in their organisation. You will get ten different answers. That variation is not a character problem. It is a definition problem.
Good performance cannot be aimed at if it has never been described. This article explains how to define what good performance looks like at the role level, how to communicate those standards, and how to make the definition consistent enough that employees across teams can predict their ratings rather than being surprised by them.
Defining good performance requires work at two levels.
Role expectations describe what the role is supposed to deliver. They include the core responsibilities, the quality standards for each, and the behaviours that define the role at the level it was designed for.
For a senior operations analyst at a Lagos fintech company, role expectations might include: produce weekly reconciliation reports by the agreed Thursday deadline with less than 0.5% error rate; attend and contribute to cross-departmental planning meetings; identify and flag operational risks before they escalate to the client.
These expectations define what meeting the standard looks like. An employee who consistently meets all of them meets expectations. One who consistently exceeds the quality and timeline standards and proactively identifies risks others miss exceeds expectations.
Once role expectations are defined, rating anchors translate those expectations into language for each rating level. A rating anchor is a description of what each level looks like in practice for a specific competency or performance dimension.
Example for the competency "Goal delivery" at a Nigerian FMCG company:
One of the most damaging communication failures in performance management is allowing employees to interpret "meets expectations" as a mediocre or default rating. In many organisations, employees assume "meets" means "average" and aspire to "exceeds" as the real success bar.
If "meets expectations" means consistently delivering against all core role requirements, that is a strong performance. A person who does that reliably is a highly valuable employee. HR and managers need to communicate this explicitly: "Meeting expectations is not a consolation prize. It means you are delivering exactly what this role requires. Exceeding expectations means you are doing that and demonstrably more."
When employees understand this, the review conversation changes. They stop feeling that "meets" is a failure and start engaging with the genuine development conversation about what it would take to go further.
Communicating performance standards should happen in the goal-setting conversation at the start of each cycle, not in the rating conversation at the end of it.
The practical conversation: "Here is what your role requires this cycle. These are the goals we are aligning to. Here is what meeting expectations looks like on each of them, and here is what exceeding expectations would require. Do you have questions about the standard before we begin?"
This conversation takes 20 minutes. It prevents 90% of the surprise and dispute that characterises poorly communicated rating cycles. It also creates a shared contract that both parties can refer to throughout the year.
In many African organisations, particularly in people-facing, coordinative, or administrative roles, defining measurable performance standards is harder than in sales or engineering. "Good communication" is a role expectation for almost every role; defining what it looks like at the meets versus exceeds level is the design challenge.
The most practical approach: use observable behaviours rather than abstract qualities. Not "communicates well" but "provides written status updates on projects by the agreed Monday deadline; raises concerns to the relevant stakeholder before they escalate; prepares meeting materials at least 24 hours in advance." These behaviours are observable, dateable, and discussable without ambiguity.
Role expectations define the permanent, ongoing standard for the position: what good work looks like in this role at this level. OKRs are time-bound goals that describe what the organisation or team is trying to achieve in a specific quarter. Both are needed for a complete performance standard: role expectations tell the employee what quality bar to maintain; OKRs tell them what to prioritise achieving. An employee can meet role expectations and miss their OKRs (delivered well, aimed at the wrong thing) or hit OKRs and not meet role expectations (achieved the goals but in a way that damaged relationships or quality). Both dimensions matter.
Role expectations should be reviewed annually or whenever a role changes significantly. In fast-growing Nigerian and Kenyan companies where roles evolve faster than formal documentation tracks, a brief annual review of role expectations before the first review cycle of the year prevents the problem of evaluating employees against a standard that no longer reflects what the role actually requires.
Good performance cannot be measured without a definition of good. The definition takes two forms: role expectations that describe the permanent standard, and rating anchors that translate each rating level into observable examples.
Both can be built without an expensive competency framework or consultant. They require one department head session to draft, one manager review session to sense-check, and one communication to employees at the start of the cycle. That investment pays back in clearer review conversations, fewer disputes, and employees who can actually orient their work toward the standard they are being evaluated against.
.png)
