When expectations are vague, every rating is a surprise. Here is how to set performance expectations that are specific enough to make ratings feel fair and predictable.
Marketing Lead
April 11, 2026
•
6 Mins Read
The most common cause of rating disputes is not bias. It is ambiguity.
An employee works hard for six months, receives a "meets expectations" rating, and feels blindsided. The manager is confused by the reaction. From their perspective, "meets expectations" is a good rating: the employee did their job.
From the employee's perspective, nobody ever told them what "exceeds expectations" would have required. So they assumed hard work would get them there.
That gap is an expectations problem, not a performance problem. This article explains how to set expectations that connect directly to your rating scale, so that every rating the employee receives was one they could have predicted.
When performance criteria are vague, ratings become a manager's opinion dressed up as an evaluation. The employee cannot prepare for them, cannot predict them, and cannot learn from them in a useful way.
In Nigerian SMEs, this pattern is especially common. A 2025 analysis of performance management practices across African organisations found that small businesses often struggle with defining clear performance metrics, and that without structured criteria, employee assessments become biased and inconsistent.
Three signals that your expectations are too vague:
These describe what the role is supposed to deliver. They include the core responsibilities, the quality standards, and the behaviours that define the role at the level it was hired for.
For a content manager at a Lagos-based fintech, role expectations might include: producing two high-quality articles per week on brief, maintaining an average quality score of 7+ from the editorial review, and briefing the design team at least five days before a campaign deadline.
These are not goals. They are the baseline. An employee who consistently meets these expectations "meets expectations."
Once role expectations are defined, the rating scale needs to describe what each level looks like in practice, using examples from the role.
A useful format:
Telling employees that "meets expectations is a good rating" is not enough. Showing them, with examples, what the difference between meets and exceeds actually looks like in their specific role is what allows them to aim accurately.
A rating anchor is a description of what each rating level looks like for a specific competency in a specific role. It makes the standard visible and comparable across managers.
The Behaviorally Anchored Rating Scale (BARS) is the most structured version of this approach. It matches each rating point on the scale to a specific example of observable behaviour. Most African HR teams do not need the full BARS methodology, but they can build a simplified version in an afternoon.
Common examples for most roles: goal delivery, quality of work, collaboration, communication, and problem-solving. For management roles, add people development and strategic thinking.
For goal delivery in a sales role:
Before the quarter begins, every employee should have access to the rating anchors for their role. This conversation: "here is what meets expectations looks like for you this cycle, and here is what exceeds expectations would require" should happen in the goal-setting meeting, not the rating meeting.
OKRs (Objectives and Key Results) provide the clearest possible bridge between performance expectations and ratings.
A well-structured OKR tells the employee: here is the direction we are moving, here is what we are trying to achieve, and here is how we will know we succeeded. When ratings at the end of the cycle connect directly to key result attainment, the employee can track their own trajectory from the first day of the quarter.
A useful mapping:
Talstack's Goals module supports this connection directly: OKRs are set at the start of the cycle, progress is tracked mid-cycle, and the completion data feeds into the performance review at the end. Managers are not reconstructing the year from memory; they have a documented trajectory that makes rating conversations faster and less contested.
Table: Expectations-to-rating alignment (template)
Performance expectations describe the overall standard the role should consistently deliver. KPIs are the specific, measurable indicators that track performance against those expectations within a given period. Think of expectations as the permanent definition of the job and KPIs as the quarterly proof that the job is being done at the right level.
Every role has some aspect that can be observed, even if it cannot be easily counted. For a people operations manager, measurable expectations might include: cycle time for HR processes, employee satisfaction scores, and recruitment time-to-fill. Behavioural expectations cover quality dimensions: clarity of communication, reliability of commitments, and quality of documentation. The mix of measurable and observable criteria covers most roles that seem difficult to rate.
Be honest with the employee. Say: "I did not define expectations clearly enough at the start of this cycle, which makes it hard to give you a fully fair rating now. Here is my assessment based on what I observed. Going forward, here is exactly what each rating level will require." That honesty is more credible than pretending the expectations were clear all along.
A rating is only as credible as the expectations it was measured against. If employees could not have predicted their rating at the start of the cycle, the problem is not their performance. It is the system.
Defining role expectations, building rating anchors, and connecting them to OKRs before the cycle begins turns performance reviews from a source of annual anxiety into a predictable, development-focused conversation that employees can prepare for and act on.
