---
name: performance-review-meeting
description: Use when asked to plan or run a formal performance review meeting — evaluating an employee's work against expectations over a defined period — as distinct from a regular one-on-one's ongoing, informal check-ins (see one-on-one-meeting), which should mean nothing in a performance review comes as a surprise.
---

# Performance Review Meeting

A performance review meeting formally evaluates an employee's work
against expectations over a defined period (commonly quarterly, semi-
annually, or annually) — distinct from a regular
[[one-on-one-meeting]]'s ongoing, informal check-ins, though a
well-run cadence of one-on-ones is what should make a performance
review's content unsurprising to the employee.

## Preparing for one

- **Gather evidence, not impressions** — concrete examples of work,
  outcomes, and behavior over the review period, not a vague overall
  sense formed mostly from recent events (recency bias is a well-known,
  avoidable distortion in performance reviews).
- **Reference agreed expectations** — whatever goals, KPIs, or role
  expectations were set at the start of the period (see
  [[key-performance-indicators]], [[smart-criteria]] for
  writing checkable goals in the first place) — a review without a clear
  prior baseline has nothing concrete to evaluate against.
- **Seek input beyond the manager's own view** — peer feedback, or a
  structured 360-style input process, surfaces blind spots a single
  manager's perspective misses.

## During the conversation

- **Balance recognition and growth areas** — genuine positive feedback
  and honest constructive feedback both matter; an imbalanced review
  (only critique, or only praise) doesn't accurately represent
  performance or help the employee improve.
- **Be specific** — "communication could improve" is far less useful than
  a specific example and a concrete suggested change; see
  [[crucial-conversations]]'s STATE framework for delivering
  difficult, specific feedback well.
- **Make it a two-way conversation** — invite the employee's own
  self-assessment and perspective, not just a one-directional
  evaluation delivered to them.
- **Connect to concrete next steps** — a development plan, adjusted
  goals, or specific actions for the next period, not just a rating with
  no forward path.

## Why nothing here should be a surprise

If regular [[one-on-one-meeting]] conversations are happening
throughout the period, a formal review's content should largely confirm
and formalize things already discussed — a significant issue raised for
the first time in a performance review, rather than in an earlier
one-on-one, is usually a sign the ongoing feedback loop broke down
somewhere before the formal review, not a fair reflection of the review
process itself.

## Common pitfalls

- **Recency bias** — weighting the last few weeks far more heavily than
  the full review period, because they're freshest in memory.
- **Surprise feedback** — raising a significant concern for the first
  time in the formal review instead of during the period when it could
  have been addressed; see above.
- **Vague, unactionable feedback** — feedback with no specific example
  and no concrete suggested change gives the employee nothing to actually
  act on.
- **A review disconnected from previously agreed goals** — evaluating
  against criteria that were never actually communicated or agreed at
  the start of the period is fundamentally unfair to the employee being
  reviewed.
- **One-directional delivery with no room for employee input** — treating
  the review as a verdict handed down rather than a conversation misses
  the employee's own perspective on their work and constraints.

## Learn more

- [[one-on-one-meeting]] for the ongoing conversation that should make formal review content unsurprising.
- [[crucial-conversations]] for delivering difficult, specific feedback well.
- [[key-performance-indicators]], [[smart-criteria]] for setting the checkable goals a review evaluates against.