Skip to content
Playbook
AdvancedHRPeopleOpsManager

Running a talent review when nobody trusts the process

A facilitation playbook for the talent review that's become a closed-door rumor mill. Three sessions, transparent inputs, and the rituals that turn it back…

12 min read
On this page
60-Second Summary
  • When trust in talent review is gone, managers stop nominating their actual stars (won't 'waste' them on a rigged process). You have one cycle to repair it.
  • Three-session arc: inputs visible, room rules new, outputs followed-through. Skip any one and trust doesn't return.
  • Make the inputs public to managers before the room — no surprise data in calibration is the single biggest trust restorer.
  • Close the loop publicly: 'here's what the talent review changed' at the next all-hands, with two specific examples.

When managers say 'talent review is rigged', they're usually right — not because someone is gaming it, but because the inputs are invisible, the room is opaque, and the outputs are mysterious. Three sessions, done in sequence, can fix it. Skip any one and you've just held three more meetings nobody trusts.

Diagnose what broke

SymptomUnderlying issueFix this cycle
Managers stop nominating top peopleNominees never get promoted/developed afterwardVisible follow-through (Session 3)
Same names every cycleRecency + visibility biasPublic inputs (Session 1)
Decisions get 'unmade' a week laterRoom lacks decision-makers or rulesNew room rules (Session 2)
Diversity drift across cyclesBias audit missingBias check inside Session 2

Session 1 — Inputs in the open

  1. Two weeks before the room: every manager publishes their nominee list and rating evidence to a shared doc.
  2. Every manager has 1 week to read other managers' nominations and flag concerns — in writing, in the doc.
  3. HR aggregates: total nominees, % of population, breakdown by demographics and function. Shared with all managers before the room.
  4. Result: no surprises in calibration. Every challenge has been pre-aired and managers have had time to bring evidence.
Why this works

Most 'rigged' feelings come from being ambushed in the room with data the manager hasn't seen. Pre-publishing destroys the ambush and forces every challenger to do their work in writing.

Session 2 — New room rules

Five rules, stated at the top of every session
  1. 1
    Evidence or quiet
    Any rating challenge must come with one piece of evidence. 'I just feel like…' is out of order.
  2. 2
    One challenge per person per round
    Stops dominant voices from carpet-bombing one rating into oblivion.
  3. 3
    Bias check at the half
    Halfway through, facilitator pulls up the bias dashboard. Anyone can call a pattern. Pause to discuss.
  4. 4
    Skip-level overrides require write-up
    A skip changing a rating must document the reasoning within 48 hours, shared with the manager.
  5. 5
    Decisions made here are decisions
    No 'I'll think about it' reversals after the room. If you need to think, you needed to challenge in the room.

Session 3 — Outputs and follow-through

  • Within 1 week: every manager has a doc for each report covering rating, rationale, top development action — usable in 1:1.
  • Within 1 month: HiPos have a stretch assignment, low-performers have a written plan, mid-pack has development support.
  • Within 3 months: HR reports back to the manager group — what % of commitments from Session 3 actually happened. Below 70%, the next cycle's trust collapses again.
  • Within 6 months: visible promotions/role-changes from the talent review. Anonymized data shared with managers.

Rituals that keep trust

  1. Annual 'what we changed' summary, anonymized, shared at all-hands. 'Last cycle's talent review moved X people into stretch roles, identified Y development gaps, surfaced Z bias pattern we're addressing.'
  2. Post-room debrief with the manager group — 30 min, what worked, what didn't, one rule to add for next cycle.
  3. Rotate the facilitator. Different perspective every cycle keeps it from ossifying.
Written by Pawan Joshi.Sources cited inline.
First published 16 Jun 2026See site changelog →