Every manager is biased in some direction. Some rate generously to protect their team, some rate tough to signal high standards, many cluster everyone in the middle to avoid difficult conversations. The goal is not to find unbiased managers; it is to design a review process that stops individual bias from deciding outcomes. This guide sets out seven steps, in the order most companies should take them, with what to do and how to tell whether it worked.

Before you start, take two minutes with the performance review bias checker. It scores your process on eight safeguards and tells you which three fixes matter most for you, so you can skip steps you already have.

Why manager rating bias deserves attention

The evidence that ratings reflect raters is strong. In a study published in the Journal of Applied Psychology, Scullen, Mount and Goff analysed ratings of 4,492 managers by multiple raters (doi:10.1037/0021-9010.85.6.956). As summarised by Buckingham and Goodall in Harvard Business Review, 62% of the variance in those ratings could be accounted for by raters’ individual peculiarities of perception.

Bias also shows up in the words, not just the numbers. Correll and Simard’s HBR article “Research: Vague Feedback Is Holding Women Back” describes how vague, non-specific feedback can hold some groups back more than others. And Kahneman and colleagues’ work on noise shows that people applying the same guidelines can reach very different judgements on similar cases. Each of these points to the same conclusion: a review process needs structure to be fair.

Step 1: Write down what “good” means for each level

Bias thrives in ambiguity. If “meets expectations” is not written down, each manager supplies their own definition, and the definitions differ. Publish a talent bar by seniority: the minimum standard for deliverables, skills and culture at each level. Then turn it into scorecards with observable statements (“Delivers team-level KPIs without close supervision”) rather than adjectives (“strong”, “proactive”).

How to tell it worked: two managers rating the same anonymised example reach the same grade, or can point to the exact statement they disagree on.

Step 2: Rate each area separately

A single overall rating invites the halo and horns effect, where one standout trait colours everything. Rate deliverables, skills and culture separately, each against its own criteria, and calculate the overall grade from the parts. The performance review template shows the structure.

How to tell it worked: people start receiving mixed profiles (strong deliverables, developing skills) instead of uniform scores across every area.

Step 3: Require evidence for every rating

Ask for a one-line evidence note for each scorecard area: a deliverable, a behaviour, a piece of feedback. Specific evidence counters both recency (the last few weeks crowding out the rest) and vagueness. It also makes calibration faster, because the discussion starts from facts.

The evidence has to exist before review time. Encourage managers to keep short running notes from 1:1s, or to log feedback as it happens, so the review is reading, not remembering.

How to tell it worked: calibration discussions reference specific work, and fewer ratings change because “I had forgotten about that project”.

Step 4: Add a second perspective

A single rater is the highest-risk setup. Ask one other manager or a senior peer who worked closely with the person for brief input on each review. McKinsey’s 2024 article “In the spotlight: Performance management that puts people first” reports that only two in five companies in its research use both upward and downward evaluation in individual reviews, and describes 360° input as a way to build a more comprehensive fact base.

How to tell it worked: the second input changes or confirms ratings with stated reasons, rather than being ignored.

Step 5: Brief raters with examples, before every cycle

A 20-minute briefing before the cycle opens does more than a long annual training. Walk through the biases most likely to show up (recency, halo and horns, leniency, central tendency, similarity) with one concrete example each, and remind managers of the evidence rule. The performance review bias guide has examples you can reuse.

How to tell it worked: managers start challenging their own first draft before submitting it.

Step 6: Check distributions by manager

Before calibration, look at each manager’s ratings side by side. A manager whose team is almost all at the top, or almost all in the middle, is not necessarily wrong, but needs to evidence it. Paste each manager’s ratings (numbers only) into the ratings spotter to flag possible leniency, severity or central tendency.

Use the distribution as a prompt, not a quota. McKinsey describes companies shifting from forced distribution to distribution guidance, and the playbook’s guideline weights (15–25% A-players, 65–85% above bar, 0–10% underperformers) are a starting point for questions rather than a rule.

How to tell it worked: the spread of ratings across managers narrows over two or three cycles without anyone being told to hit a number.

Step 7: Calibrate with evidence on the table

Calibration is where the steps above come together. Managers present evidence for their top and bottom ratings against the bar; peers ask questions; the facilitator logs every change with a reason. Three checks matter most: generous graders, missing or thin evidence, and outliers or sudden jumps. The calibration meeting guide and the calibration meeting template show how to run it.

How to tell it worked: you can explain every final rating with evidence, and employees in different teams with similar output get similar grades.

Worked example: two managers, one standard

An illustrative product company has two engineering managers with similar teams. Manager A rates five of six engineers at the top grade; Manager B rates five of six in the middle. Before the company introduced a written bar, both distributions went straight into pay decisions, and Manager A’s team received noticeably larger rises for similar output.

After steps 1 to 3, both managers rate against the same mid-level scorecard, separately for deliverables, skills and culture, with an evidence note per area. The ratings spotter flags possible leniency for Manager A and possible central tendency for Manager B. In calibration, Manager A evidences two of the top ratings convincingly and moves three down a grade; Manager B, prompted to find their strongest performers, moves one engineer up with clear evidence of work above the bar. The final distributions still differ, but now the difference reflects the teams rather than the managers, and every change is logged with a reason both managers can explain to their reports.

What order to do this in

If your bias checker result is…Start with
HighSteps 1 and 7: a written bar and structured calibration. Without both, other fixes have little to hold on to.
MediumWhichever three fixes the checker shows; usually evidence (step 3), a second rater (step 4) or distribution checks (step 6).
LowKeep step 6 running each cycle and re-run the checker after any process change.

Common mistakes

  • Relying on training alone. Awareness helps, but ratings change most when the process changes.
  • Forcing a curve. A quota swaps one unfairness for another, especially in small teams.
  • Removing ratings entirely. Decisions on pay and promotion still get made; without ratings they are made less visibly.
  • Fixing bias in one cycle. Expect two or three cycles before distributions settle.
  • Ignoring the words. Read a sample of written reviews for vague language, not just the scores.

To see how much time your current calibration takes, use the review cost calculator. For the full method behind these steps, read the performance management framework.

Sources: Scullen, Mount & Goff (2000), Journal of Applied Psychology; Buckingham & Goodall, HBR (2015); Correll & Simard, HBR (2016); Kahneman et al., HBR (2016); McKinsey, In the spotlight (2024).

Use with this guide