How To Run A Performance Review That Actually Helps

Performance reviews are disliked by everyone involved and persist because organizations need a defensible basis for pay and promotion decisions. Most of what makes them useless is fixable.

Separate the conversations

A review that decides pay cannot also be a development conversation. Once compensation is in the room, the employee's rational strategy is to defend their record, not to explore what they find difficult.

Hold the development discussion separately, at a different time of year, with no consequences attached. This single change does more than any redesign of the form.

Remove the recency problem

A review written in December describes the autumn. Keep brief contemporaneous notes through the year — a few lines after significant pieces of work — and the review becomes a summary of a record rather than a reconstruction from memory.

Ask the employee for their own record of the year before you write yours. It surfaces work you did not see.

Be specific about the standard

Feedback fails when it describes a trait rather than a behavior against an expectation. Not that someone lacks strategic thinking, but that a specific document did not consider a specific alternative, and here is what considering it would have looked like.

The test is whether the person could act differently tomorrow having heard it.

No surprises

A serious concern raised for the first time in a formal review is a management failure, not a performance one. Anything material should have been said when it happened.

Watch the distribution

Where ratings are compared across a group, examine the pattern for bias — by gender, by ethnicity, by whether someone works remotely, by who joined recently. Differences may be legitimate; unexamined they are exactly where systematic bias operates.

Write it down

Whatever is agreed goes in writing, with dates. It protects the employee, it protects the organization, and it makes the next review a comparison rather than a fresh start.