Writing a Performance Review That Actually Means Something
Writing a Performance Review That Actually Means Something
Performance review season arrives twice a year for most organizations, and twice a year, managers sit down to write something they have been putting off for weeks. The result is usually a document that took an hour to write, will take five minutes to read, and will change absolutely nothing for the person receiving it.
That’s not because the manager doesn’t care. It’s because nobody taught them how to write a review that actually does its job.
What most reviews actually say
Pull up almost any performance review and you’ll find some version of the same language:
“Sarah is a valuable member of the team. She consistently demonstrates a positive attitude and contributes to a collaborative environment. She should continue to develop her leadership skills going forward.”
That review could describe almost anyone. It contains no specific information, no measurable observation, and no actionable direction. Sarah reads it, nods, signs the form, and goes back to her desk knowing exactly as much about her performance as she did before.
That’s a failure. Not a dramatic one, but a quiet, cumulative one that adds up across an entire organization over time.
Why vague reviews happen
There are a few reasons managers default to this kind of language, and most of them are understandable.
Writing vague reviews feels safer. Specific feedback can feel confrontational, and many managers would rather soften a critique than have a difficult conversation on paper that becomes part of a permanent record.
It’s also faster. “Strong communicator” takes five seconds to write. A specific example of how someone communicated well, in what context, and with what result takes thought.
And honestly, a lot of managers are modeling what they’ve received themselves. If every review you’ve ever read sounds the same, that becomes the template.
The problem is that safe and fast doesn’t serve anyone. Not the employee, not the manager, and not the organization.
What a useful review actually contains
A performance review that means something has three qualities. It’s specific, it’s honest, and it’s actionable.
Specific means grounded in actual events and observable behavior. Not “strong communicator” but “presented the Q2 findings to the leadership team clearly and fielded questions without preparation.” Not “needs to improve time management” but “missed three project deadlines in Q3, two of which required other team members to adjust their own timelines.” Specificity does two things. It tells the employee exactly what you observed, which makes the feedback credible. And it creates a record that’s actually useful if the review ever needs to be referenced later.
Honest means saying what’s true, including the things that are uncomfortable to write. A review that only documents strengths and buries weaknesses in vague language like “has opportunities for growth” isn’t a balanced assessment. It’s a document that protects the manager from a hard conversation at the expense of the employee’s development. If someone is struggling, the review should say so clearly and specifically. If they’re excelling, the same standard applies. Empty praise is just as useless as empty criticism.
Actionable means the employee finishes reading knowing what to do differently, or what to keep doing and why it matters. “Continue to develop leadership skills” is not actionable. “Take on one cross-functional project in Q1 to build experience managing people outside your direct team” is.
The difference is the difference between a direction and a destination. One tells the person where to go. The other just waves vaguely toward the horizon.
The language patterns worth cutting
A few phrases that show up in almost every review and should be reconsidered every time:
“Demonstrates a positive attitude” — What does this mean specifically? What did they do that reflected it? If you can’t answer that, the phrase isn’t earning its place.
“Has opportunities for growth” — This is corporate for “there’s a problem I don’t want to name.” Name it.
“Is a valued member of the team” — Almost certainly true of the person you’re reviewing. Also true of every other person on your team. It adds nothing.
“Should continue to develop” — Continue from where? Develop toward what? This phrase gestures at a direction without pointing to anything.
“Goes above and beyond” — Doing what, specifically? When? This is the kind of praise that feels good to receive and evaporates immediately because it has no weight behind it.
A quick rewrite
Here’s the same review from earlier, written with specificity and honesty:
“Sarah took on the vendor onboarding project in Q2 without being asked, built the process documentation from scratch, and trained two new team members on it in the same quarter. That kind of initiative isn’t something she was hired to do, and it made a real difference to how the team operates. Where she has room to grow is in communicating when she’s overloaded. There were two instances this quarter where she took on more than she could handle without flagging it, which created avoidable bottlenecks. The goal for next quarter is to raise that flag earlier rather than absorbing the pressure quietly.”
That review is still positive. It’s also honest, specific, and gives Sarah something concrete to work with. It respects her enough to tell her the truth.
The standard worth holding yourself to
Before you submit a review, ask one question: if this person left the company tomorrow and someone read this review to understand who they were and how they performed, would it tell them anything real?
If the answer is no, rewrite it. The review exists to serve the employee’s development and the organization’s memory. Vague language serves neither.
It takes longer to write a review that means something. It’s worth the extra time.