How to Write Performance Reviews for Employees (That Actually Land)

It's review season again. You've got a blank form open, a person's whole year staring back at you, and a deadline from HR that's closer than you'd like. You want to be fair. You want it to actually help. But mostly you want it to be over. So you copy last year's language, soften the hard parts, and hit submit. Then you wonder why nothing changes.

I get it. Writing performance reviews for employees is one of the tasks managers dread most, and for good reason: nobody ever taught you how. You were promoted for being good at the work, then handed a blank evaluation and told to judge another human’s twelve months on the job.

The external problem is the form itself: you don’t know what to write or how to say it. The internal problem is heavier. You’re afraid of being unfair, of demoralizing someone who tried hard, of a tense conversation that follows you around the office for a month. So you play it safe and vague. And vague is exactly what makes reviews useless.

I spent twenty years in the military being evaluated and evaluating others, then built and ran a seven-figure company where I wrote a lot of these. Now I coach managers through the same knot you’re in. Here’s the good news: a review that lands isn’t about better adjectives. It’s about a structure you can reuse every time.

Read that middle number again. A fifth of the time, the review you sweated over made things worse. That’s not because feedback is bad. It’s because a vague, once-a-year verdict with no examples feels like a judgment instead of a map. Let’s fix the map.

Why most performance reviews fail

Most reviews die from the same disease: generality. “Great team player.” “Needs to improve communication.” “Exceeds expectations.” None of it points to a single real moment, which means the person can’t repeat what worked or fix what didn’t. They just walk away with a grade and a vague feeling.

The second killer is surprise. If the annual review is the first time someone hears about a problem you’ve been sitting on since March, you’ve failed them twice: once by staying quiet, and once by ambushing them in writing. A review should be a summary of conversations you’ve already had, not breaking news.

A simple structure for writing a review that lands

You don’t need a psychology degree or corporate buzzwords. You need to answer three questions for every point you make, in order. This is the frame I teach every manager I coach.

1. What did they actually do? Anchor to specifics

Open your notes (or your memory) and find the real moments. Not “handled projects well,” but “took over the Reynolds account in April when it was slipping and pulled it back on schedule.” Specifics prove you were paying attention, and they give the person something concrete to be proud of or to build on. If you can’t name an example, you’re not ready to write the line yet.

2. What did it produce? Tie behavior to impact

A behavior only matters because of what it caused. Connect the two out loud: “Your habit of over-preparing for client calls is why we closed two renewals nobody expected.” Now it’s not your opinion. It’s cause and effect. This works for growth areas too: “When updates came late, the team downstream sat idle, and we missed the launch window twice.” You’re not attacking the person; you’re showing them the ripple they couldn’t see.

3. What happens next? Set one or two clear goals

End every review pointing forward, not just backward. Pick one or two specific, achievable goals for the next cycle, not a laundry list. “Own the weekly status update so the team stops chasing you for it” beats “improve communication” every time, because the person knows exactly what success looks like on Monday.

Performance review examples you can adapt

The structure is easier to see in finished lines. Here’s the difference between vague and useful.

Instead of “great communicator,” write: “Your Monday recaps became the one document the whole team trusted. Three people told me they plan their week around it.” Instead of “needs to be more proactive,” write: “When a blocker showed up, you tended to wait for me to notice. I’d like you to flag it the same day and bring one proposed fix.” Instead of “exceeds expectations,” write: “You didn’t just hit your number. You rebuilt the onboarding checklist that’s now saving every new hire a week.”

Notice the pattern: a real moment, its impact, and where relevant, the next step. That’s a performance review phrase that actually moves someone. And balance the ledger: if the whole document is corrections, the person hears only that they failed. Specific praise isn’t fluff; it tells people exactly what to keep doing.

How to prepare so next year’s review writes itself

The reason reviews feel impossible is that most managers try to reconstruct a year from memory the night before the deadline. Don’t. Keep a running note on each person: a line after every finished project, every piece of feedback, every win or stumble. Ten seconds a week. When review time comes, the examples are already there and the document nearly writes itself.

And keep the hard stuff off the form until it’s been said out loud. The most useful thing you can do before writing a formal year-end review is have the real conversation in a one-on-one first, so the written version only confirms what the person already knows.

What a good review actually buys you

Here’s what’s at stake. Phone in the reviews and you get what you’ve always gotten: people who don’t know where they stand, quietly stop growing, and eventually leave, because good people don’t stay long with a manager who can’t tell them the truth about their work.

Do it well and something quieter happens. People start trusting that when you evaluate them, it’ll be fair, specific, and honest. That trust is the bedrock of every strong team I’ve ever seen. Your best people push harder because they know good work gets noticed by name, and your strugglers actually improve because, for once, they know exactly what to fix.

You don’t have to be harsh to be honest, and you don’t have to be soft to be kind. Anchor every point to a real moment, tie it to its impact, and end pointing forward. Do that, and review season stops being the week you dread, and becomes the week your team finds out you were paying attention all along.