A performance review is a formal assessment of an employee's contributions over a defined period, evaluated against agreed goals and team-level outcomes.
Most reviews combine a written record with a face-to-face conversation. The written record documents what happened; the conversation determines what happens next. When reviews are treated as paperwork exercises, they lose their ability to change behavior or inform promotion decisions.
Key takeaways
- The conversation matters more than the rating: a number without a clear narrative leaves the person unsure what to do differently.
- Tie individual performance to team outcomes, not just task completion.
- A review that surprises the employee means feedback has been absent all year.
- Document the decision logic, not just the result, so the record is useful in future cycles.
Why it matters
Performance reviews are the formal moment where informal signals get converted into recorded decisions. Promotion eligibility, compensation adjustments, performance improvement plans: all of these depend on review records that are specific, evidence-based, and tied to business outcomes. A vague review protects no one.
Managers who treat reviews as a compliance event miss the leverage point. The review conversation is one of the few structured opportunities to align expectations explicitly, surface obstacles the manager has not seen, and give feedback that the employee will take seriously because of the formal context.
The quality of a review also signals the manager's observational depth. If you cannot describe your report's impact on the team's output with specifics, you have not been watching closely enough. That gap is information too.
How it works in practice
How to run a review that changes behavior
-
Gather evidence before you write anything
Pull meeting notes, project outcomes, peer input, and the goals agreed at the last cycle. The review should cite what actually happened, not your general impression of the person.
-
Lead with impact, not activity
Frame everything in terms of what the person's work produced for the team and the business. 'Completed 12 features' is activity. 'Reduced integration errors by 40% over Q3, which unblocked the platform migration' is impact.
-
Name the specific gaps
Avoid softening language that obscures the real message. If someone missed commitments repeatedly, that needs to be stated directly, with examples, not buried under qualifications.
-
Make the forward ask explicit
End the written review with one to three specific behavioral changes or outcomes you expect in the next cycle. Vague encouragement produces no change.
-
Separate the rating conversation from the development conversation
When rating and development are conflated, people stop listening after they hear the number. Schedule a follow-up conversation specifically about the next cycle if needed.
Common mistakes
Rating without explanation
A score without a narrative leaves the employee guessing. They will fill in the gap with their own interpretation, which is often less accurate than the truth.
Surfacing surprises
If the review contains feedback the person has never heard before, the review is not the problem. The problem is the absence of feedback across the previous six or twelve months.
Comparing to peers instead of expectations
Relative rankings tell people where they stand in the room, not whether they met the standard. Calibrate against role expectations and team outcomes, not against whoever happened to be on the same team.
Treating the form as the deliverable
A completed review template is administrative overhead. The deliverable is a clear shared understanding of what happened and what changes next.
What it sounds like
Q4 review conversation. Daniel manages software engineering. Merav is a senior engineer. Guy is observing as part of a leadership calibration.
Daniel: “Merav, the delivery numbers are solid, but what I want to talk about is the two escalations in October. Both involved decisions you could have made without me, and both stalled for three days waiting for my sign-off. That cost the team time we didn’t have.”
Merav: “I didn’t want to overstep. The risk felt higher than usual on both of those.”
Guy: “That’s useful to hear. Daniel, can you name what ‘decision authority’ looks like for Merav’s level, so there’s no ambiguity about when she should act and when she should escalate?”
Questions managers actually ask
How long should a written performance review be?
Long enough to document the evidence and the decision logic, short enough to be read in under 10 minutes. Three to five paragraphs is usually enough. Length is not a proxy for rigor.
What do I do if I haven't been giving feedback all year and now the review is due?
Write the most accurate review you can based on the evidence available. Then use the review conversation to name the gap explicitly: the person deserved more feedback earlier, and you will address that in the next cycle. Inflating the rating to avoid discomfort makes the next correction harder.
How do I handle a review for someone I know is underperforming but haven't documented yet?
Document now. A review is a record. Write what you observed, with specifics, even if it is late. A review that glosses over performance issues because you didn't address them earlier is a liability, not a kindness.
Should I share the written review before the conversation?
Yes, if your process allows it. People absorb difficult feedback better when they have had time to read it before responding. Walking someone into a negative review cold rarely produces a useful conversation.
How do I rate someone who did excellent work on the wrong things?
Distinguish between quality of execution and alignment to priorities. Someone can be a high-quality executor who spent the cycle on the wrong bets. Both things are true and both belong in the review.
What if the employee disputes the rating?
Hear the dispute, ask for the specific evidence they believe was missed, and update the record if the evidence changes the assessment. If it does not, explain why. The conversation is not a negotiation, but it should be a genuine exchange.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.