The Clean Line: Keeping OKRs Out of the Appraisal Room

OKRs are designed to make priorities visible, encourage stretch and help teams learn quickly. Annual appraisals are designed to support pay decisions, promotion judgements and formal performance records. Those are different jobs. When UK managers quietly merge the two, the OKR set stops functioning as a tool for focus and starts behaving like an appraisal form in disguise. Teams notice quickly. They begin to ask whether a key result will be graded, whether a missed target will affect a bonus and whether ambition is safe.

The result is predictable. Objectives become cautious. Key results are padded. Confidence scores are managed for appearance rather than insight. Managers spend review meetings defending ratings instead of discussing learning. The organisation may still say it wants stretch goals, but the paperwork rewards defensiveness.

A clean separation is not an argument against accountability. It is an argument for putting accountability in the right conversation. OKRs should be reviewed for learning, prioritisation and adjustment. Performance, pay and promotion should be reviewed through a separate process with different evidence, different language and a different cadence. For UK SMEs without large HR functions, the boundary needs to be explicit, simple and repeatable.

Why appraisal gravity distorts OKRs

Appraisal systems have gravity. They carry consequences. Even when managers say an OKR review is informal, team members will read the surrounding signals: whether completion percentages appear in appraisal forms, whether bonus discussions reference objective attainment and whether promotion cases cite key results as a scorecard.

Once OKRs enter that gravity field, three distortions usually follow. First, teams sandbag. They choose key results that can be comfortably achieved rather than results that would genuinely move the business. Second, managers avoid difficult objectives because unfinished work looks like poor performance. Third, learning disappears from reviews because nobody wants to document uncertainty in a system that may later judge them.

The problem is not that OKRs involve ambition or measurement. The problem is mixing a learning instrument with a judgement instrument. A football coach may review match footage to improve the next performance; that is not the same as deciding a player's contract. UK managers need the same distinction.

Warning signs that your OKR set has become an appraisal form

Diagnose the boundary before rewriting the process. The following signs suggest that OKRs and performance management have become entangled.

• Key results are written as personal competency statements rather than business outcomes.
• Managers ask whether an objective will be graded before agreeing to it.
• Confidence scores are discussed alongside bonus or pay review timelines.
• Appraisal forms ask for an OKR completion percentage.
• Teams routinely revise objectives after results are known so that the record looks stronger.
• Individual OKRs are cascaded so tightly that every rating can be traced to one person.
• Review meetings spend more time on evidence for ratings than on evidence for learning.
• High performers avoid stretch objectives because failure carries a reputational cost.

If several of these are present, the issue is structural rather than cultural. A stronger exhortation to be ambitious will not fix it. The process needs a clean line.

A two-meeting format for UK SMEs

The simplest separation is a two-meeting format. Keep the meetings distinct in purpose, attendance, documentation and cadence.

Meeting one: the OKR learning review

Hold this quarterly, or monthly for fast-moving teams. The purpose is to review progress, confidence, blockers and learning. It should include the team closest to the work and the manager responsible for priorities. It should not produce a performance rating.

Use four questions:

• What have we learned since the last review?
• Which key results are on track, and what evidence supports that view?
• What has changed in the business that should change our priorities?
• What support or decision does the team need now?

Record actions, changes to key results and decisions. Do not record a rating. If an objective is no longer useful, say so and replace it. That is a sign of a healthy review, not a failure.

Meeting two: the performance and development review

Hold this separately, perhaps twice yearly, with the line manager and employee. Its evidence should include agreed competencies, delivery record, feedback from colleagues, development goals and conduct. It may reference OKR work as an example of judgement or collaboration, but it should not use OKR completion as a formula for pay or promotion.

The sequencing matters. Avoid holding the OKR review immediately before an appraisal meeting. Give the two conversations separate calendars and separate forms. If managers need a simple rule, use this: OKR reviews decide what we do next; performance reviews decide how we recognise and develop people.

A one-page agreement for 2026

UK SMEs can formalise the boundary without creating bureaucracy. A one-page agreement, signed by the leadership team and shared with managers, is enough. It should state:

• Purpose: OKRs are a prioritisation and learning tool, not a rating mechanism.
• Scope: team OKRs are reviewed in OKR meetings; individual performance is reviewed in appraisal meetings.
• Evidence: OKR attainment percentages will not be used as a direct input to pay, bonus or promotion decisions.
• Cadence: OKR reviews occur quarterly or monthly; performance reviews occur separately.
• Records: OKR notes and appraisal forms are kept as separate documents.
• Exceptions: any decision to use an OKR example in a performance discussion must be transparent and contextual, not mechanical.
• Review: the leadership team will review this agreement in December 2026.

The agreement should be short enough to be read. Its value lies in making the boundary visible, especially for new managers who inherit mixed messages from previous appraisal cycles.

Scripts for resetting the boundary

Changing the process requires managers to explain it without sounding as if accountability has been removed. These scripts can help.

When introducing the separation to a team:

Our OKR review is for learning and prioritisation. It does not determine pay, promotion or your performance rating. Those conversations happen separately, with different evidence. If an objective needs to change, we will discuss that openly.

When a team member asks whether a key result will be graded:

The key result helps us judge whether the work is moving the business. It is not a grade for you. We will use the review to decide what to continue, stop or change.

When a manager is worried that separation weakens accountability:

We are not removing accountability. We are separating two questions: what should the team do next, and how should we recognise individual performance. Mixing them makes both weaker.

When HR or a director wants to include OKR completion in an appraisal form:

We can reference OKR work as context, but we should not use completion percentages as a rating input. That would encourage sandbagging and undermine the stretch we say we want.

The test for 2026

The practical test is simple. Ask a team member whether they would feel safe proposing an ambitious key result that might not be fully achieved. If the answer depends on when the appraisal form is due, the boundary has failed. If the answer is yes because the OKR review is genuinely for learning, the separation is working.

OKRs should make important work visible, not make people defensive. UK teams can keep the ambition and keep the accountability by giving each conversation its own room, its own evidence and its own purpose.