How to run a performance review that doesn't waste everyone's time

The reviews people dread are the ones that either surprise them or tell them nothing they did not already know.

The first type surfaces critical feedback the employee has never heard before. The second is a structured retelling of things everyone already knows, followed by the same goals as last year. Both waste time and undermine confidence in the process.

A good performance review is not a difficult conversation, it is a well-prepared one. Most of the work happens before the meeting, and most of the value comes from listening rather than presenting. Here is a practical process that makes both sides feel like it was worth the time.

Step 1: Gather context before you prepare

Pull together the goals set at the last review, feedback you have given and received during the period, and any documented highlights or concerns. Do not rely on memory, your memory will be biased toward recent events and emotionally charged moments.

Look at the evidence: what did this person actually deliver? What did you observe? What did others share? Build a picture from what happened, not from your general impression of the person.

This step takes most managers longer than they expect. That is a good sign, it means you are taking it seriously.

Step 2: Give the employee time to self-assess

Before the review, send the employee a brief set of questions to think through. Ask them:

• What are you most proud of from this period?
• Where did you find things most challenging?
• What do you want more or less of in your work?
• What support do you need from your manager?

Give them at least a week to reflect and respond. Their answers will shape the conversation. When a manager starts the review by sharing the employee's own self-assessment, it shifts the dynamic, the employee is not on trial, they are part of a shared analysis.

Step 3: Prepare your own perspective

Write specific examples for the points you want to cover, both strengths and development areas. Do not write general statements. Each point needs a real situation attached.

"Strong communicator" is not a point. "In the Q3 client presentation, you flagged the budget risk early enough that the client could process it before the ask, that made a visible difference to how they received the proposal" is a point.

For development areas, prepare them as observations and questions rather than verdicts. "I noticed you tend to take on tasks that could be delegated, I'm curious what drives that" opens a conversation. "You need to delegate more" closes one.

Step 4: Have the conversation

Start by listening. Share the employee's self-assessment back to them, ask if they want to add anything, and let them speak first. Then add your own perspective, where you see it the same way, where you see it differently, and what additional context you bring.

Keep the conversation specific. For every point, tie it to a real example. If you cannot, ask yourself whether the point is really yours to make.

Save development goals and next steps for the second half of the conversation. Spend the first half on what happened and what it means. Rushing to goals before you have shared a full picture of the period cuts the most valuable part of the review short.

Step 5: Document what was discussed

Write a brief summary of what was agreed, goals for the next period, development areas, and any follow-up actions. Keep it short: a page is usually enough. Send it to the employee the same day, while the conversation is still fresh.

Documentation is not bureaucracy. It is the thing that turns a good conversation into something both people can hold each other accountable to. Without it, the review evaporates within a week.

Step 6: Follow through

Check in on the agreed goals at the next 1:1. A review that ends with agreed actions and no follow-up teaches employees one thing: the process does not actually matter.

You do not need a formal process for follow-through. You need to bring the goals up, ask how they are going, and respond to what you hear. That is enough to signal that the review was real.

Common mistakes

• Delivering feedback for the first time in the review. If the employee is hearing something critical for the first time in a formal review, you have waited too long. Feedback should have been given when the situation was fresh.
• Rating without examples. Any rating or assessment without a specific example attached is an opinion, not an evaluation. Employees have a right to know what evidence led to a conclusion.
• Skipping the employee's perspective. A review that is 90% manager presentation and 10% employee response is a one-way broadcast, not a performance conversation.
• Setting goals in the last five minutes. If you run out of time for goal setting, schedule a separate conversation for it. Goals agreed in a rush are goals that do not stick.

Frequently asked questions

How long should a performance review take?

A one-hour conversation is usually sufficient for most roles. Preparation takes longer, expect to spend 30 to 60 minutes gathering context and preparing specific examples before the meeting. For more senior roles or complex periods, 90 minutes for the conversation itself is not unusual.

What questions should you ask in a performance review?

Ask what they are most proud of, where they found things most challenging, what they want more or less of in the next period, and what support they need from you. These open-ended questions produce more useful conversations than rating scales or structured competency frameworks.

How do you give critical feedback in a performance review?

Use specific examples and describe the impact, not the intent. Say what you observed and what effect it had, not what you think motivated it. Then ask what the employee thinks happened. Most critical feedback lands better as a question than a statement, because it keeps the conversation open.