Before a performance review, an employee should already know what was expected of them, how it would be judged and what good looked like. When that is true, the review is a conversation about evidence. When it is not, the review becomes the first time the employee hears the standard, and it is judged after the fact.
Most disagreement in reviews comes from this gap rather than from the rating scale or the form. A manager rates someone down for something they never said mattered, or rates them up for effort that was never the point. Neither is dishonest. The expectation was simply never written or agreed.
What an expectation needs to say
An expectation is clear when the employee and the manager would describe it in roughly the same words. Four parts usually make that happen:
- The outcome: what should be true by the end of the period, for example orders processed within the agreed time or a team's attendance records closed on the due date.
- The standard: how well, how accurately or how often, in terms someone could check.
- The way of working: the behaviours that matter, such as raising problems early or handing work over completely.
- The limits: what the employee can decide alone and what needs approval.
Compare this with 'be proactive' or 'take ownership'. These describe a quality without saying what it looks like on a Tuesday. If two managers would give different examples of it, it is not yet an expectation.
Agree them in a conversation, not an email
An expectation that arrives as a document the employee never discussed is an instruction, not an agreement. Set aside a short conversation at the start of the period, or when the role changes. Ask the employee to say it back in their own words, and ask what would get in the way. Obstacles raised here are cheaper to fix than the same obstacles discovered in the review.
- 1
Draft before you meet
Write the three to five expectations that matter most for the period. More than that usually means none of them is prioritised.
- 2
Discuss them
Ask what is unclear, what resources are missing and what the employee thinks good looks like.
- 3
Write down what you agreed
One page, in plain language, held by both people. Not the version you drafted, but the version you agreed.
- 4
Revisit when work changes
A change of priority, a new system or a new team changes the expectations. Update the page the same week.
- 5
Check in before the review
A short mid-period conversation where nothing is rated, but the employee hears how it is going against what was agreed.
Link expectations to the role
Expectations should sit inside the role's accountabilities, not replace them. If the role itself is vague, the expectations will be too. Job descriptions that make accountability visible covers how to write the role so that individual expectations have something to attach to.
What to do when the review finds a gap
If a review surfaces a gap against an expectation, first ask whether it was clear, agreed and revisited. If it was, the gap is a performance conversation. If it was not, the gap belongs partly to the manager, and the useful response is to fix the expectation and agree a fresh period, not to record a low rating.
A short test before every review
- Can the employee state their main expectations without looking at a document?
- Would the employee's manager and the manager's manager describe them the same way?
- Was each one agreed before the work started, not added during the review?
- Has anything changed since they were written that makes one of them out of date?
If the answer to any of these is no, fix that first. Then run the review, and use the appraisal cycle to keep it consistent across the team.
