Giving a performance review well means the person sitting across from you is not hearing anything for the first time. If a rating or a piece of hard feedback lands as a surprise, the review has already failed, regardless of how carefully the meeting itself is run. This guide is for the manager's side of the table: how to prepare, structure the conversation, deliver feedback that holds up, and leave the person with a plan rather than just a verdict.
What changed in 2026
- Continuous feedback tools feed the annual review more directly, so a well-run review increasingly summarizes a paper trail rather than introducing new information.
- AI draft-assist for writing reviews became common, which speeds up the writing but still requires a manager to edit for accuracy — generic AI-smoothed language is easy for employees to spot and easy to resent.
- More companies split the rating conversation from the compensation conversation into separate meetings, so neither discussion gets rushed or overshadowed by the other.
Prepare before the room: calibration and evidence
Walk in with specific examples, not adjectives. "Strong communicator" is an impression; "walked a confused client through the migration plan twice without losing them" is evidence. Before the conversation, calibrate the rating against peers doing similar work — a rating that has not been checked against comparable performance elsewhere in the team is one you will struggle to defend if it is questioned later.
Structure the conversation
Open by asking how the person thinks the period went before delivering your own assessment; it surfaces where your views already align and where the real conversation needs to happen. Cover strengths with specific examples, then areas for growth with the same specificity, then move to the forward plan. Leave real time for the person to respond — a review that is entirely one-directional is a monologue, not a conversation.
Deliver hard feedback without softening it into mush
The instinct to wrap criticism in praise on both sides — the "feedback sandwich" — often blunts the message so much the person leaves unsure anything needs to change. Feedback that names the specific situation, the behavior, and the impact lands more clearly and is easier for the other person to actually act on.
| Approach |
What it does well |
Risk |
| Feedback sandwich |
Softens the emotional hit |
Core message often gets lost or minimized |
| Situation-behavior-impact |
Specific and actionable |
Needs real preparation to execute well |
| Strengths-first |
Builds receptiveness before hard news |
Can read as a setup if overused |
| Priorities-first |
Nothing gets buried at the end |
Can feel abrupt without a warm opening |
After the review: the forward plan
A review that only scores the past wastes the one guaranteed uninterrupted hour you get with this person. Close with two or three concrete priorities for the next period, and a specific date to check on them — not at the next annual cycle, but soon enough that the plan is still a plan and not a memory. If skill gaps came up, connect them to real development, not just a comment logged in the system; see how to build a learning culture in 2026 for how that connects to the team's broader growth habits.
Common mistakes
- Saving hard feedback for the review. Stockpiling criticism for one annual conversation is unfair to the person and far less useful than addressing it when it happened.
- Skipping calibration. An uncalibrated rating is a guess dressed up as a decision, and it shows the moment it gets compared to anyone else's.
- Talking the entire time. A review the manager delivers as a monologue misses what the other person actually thinks and needs.
- Ending without a plan. A rating with no forward priorities leaves the person with a grade and nothing to do about it.
FAQ
How much should a performance review be a surprise?
Ideally, not at all. If ongoing feedback is happening throughout the period, the review should read as a structured summary, not breaking news.
Should ratings be discussed before compensation in the same meeting?
Where possible, separate them. Combining a performance rating with a pay conversation in one sitting tends to let one topic dominate and drown out the other.
What if the employee disagrees with the rating?
Let them respond and explain their view fully before defending the rating. If their evidence genuinely changes the picture, recalibrating is more credible than defending a position that no longer fits the facts.
How specific should feedback examples be?
As specific as you can make them. A vague impression is easy to dismiss; a named situation, behavior, and impact is much harder to argue with and much easier to act on.
Where to go next