Performance review season has a way of bringing out the worst in everyone - managers who procrastinate, employees who rate themselves too high or too low, and HR teams who spend more time cleaning up reviews than they ever expected to.

The frustrating part is that most of the problems are preventable. Not because performance reviews are easy, but because the same mistakes show up year after year - and most managers don't even know they're making them.

Here's what to watch for, and what to do instead.

Your words will outlast the moment

This is something most managers don't think about when they sit down to write a review. Whatever you put in that document doesn't disappear after the conversation is over. It lives in an HR file. It gets referenced in promotion decisions. It becomes evidence if a performance situation escalates - or if an employee ever files a claim.

That doesn't mean you need to write like a lawyer. It means you need to write like someone who'd be comfortable with anyone reading it. Your employee, their next manager, an HR leader, a mediator. If something would make you think twice (or even cringe) in that context, rewrite it before you submit.

The good news is that the standard for a well-written review isn't complicated. It's specific, factual and fair. That's it.

Vague language is the most common problem — and the easiest to fix

"Great attitude." "Needs to be more detail-oriented." "Good team player." These phrases appear in performance reviews constantly, and they're almost useless.

Not because the observations are wrong. Often they're right. But without a specific example attached, they don't mean anything the employee can act on - and they don't mean anything you can stand behind.

The fix is simple: for every general statement, ask yourself what actually happened. What did you see? When? What was the impact? That's your example. That's what goes in the review.

"Strong communicator" becomes "led the Q3 client debrief when the project hit a difficult moment and kept the relationship intact." "Not detail-oriented" becomes "submitted three reports in Q2 with data errors that required last-minute revisions before client delivery." Both of those are things a person can actually do something with.

Specificity isn't about being harsh. It's about being useful - whether the feedback is positive or critical.

Recency bias is costing your employees a fair review

Here's a scenario that plays out in organizations everywhere: a manager sits down in February or March to write an annual review. The last two months are fresh. Everything before that is a blur.

So the review ends up being a reflection of the last quarter - good or bad - rather than the actual year. An employee who had a strong spring and a rocky fall gets a tougher review than they deserve. An employee who had a slow start but finished strong looks like a top performer on paper.

Neither of those is an accurate picture, and neither is fair.

The best thing you can do to fight recency bias is to keep a running note throughout the year. It doesn't have to be formal. A shared doc, a folder of saved emails, a note in your phone. Any time something notable happens - a win, a miss, a moment of growth - write it down with a date, why it mattered and what they learned. When review time comes, you have the full year in front of you instead of just what you can remember.

If you don't have that system yet, before you write a single review this season, spend ten minutes scrolling back through your calendar and emails from January through September. You'll be surprised what you now remember - and can use.

Your ratings and your comments need to tell the same story

This is one of the most overlooked problems in performance reviews, and it creates real confusion (and worse) for employees.

A manager checks "meets expectations" but writes comments that clearly describe someone who went above and beyond. Or rates someone "exceeds expectations" in every category, but has been meaning to have hard performance conversations with them all year.

Employees read both. When they don't match, trust breaks down. The employee either feels shortchanged by the rating or confused by the disconnect. And if the review is ever used in a future employment decision, the inconsistency creates problems.

Before you submit, do a quick check. Read each rating alongside the comments for that section. Do they match? Does the overall rating reflect the overall narrative? If not, something needs to change - either the rating or what you've written.

What nobody tells you about positive reviews

Most managers spend a lot of energy worrying about how to deliver tough feedback. Positive reviews feel easier - but they also need to be written thoughtfully.

The biggest one is that positive feedback delivered vaguely doesn't actually resonate. "You had a great year" is nice to hear, but it doesn't tell the employee what to keep doing, what to build on or why their work mattered. It also doesn't give them anything to point to when they're being considered for a promotion or a new opportunity.

Strong positive reviews do two things that weak ones don't. They name the specific behaviors and contributions that drove results. And they connect those things to impact - on the team, on the organization, on a project or a client. That's what turns a feel-good review into a genuinely useful one.

The documentation habit that changes everything

One of the most practical things any manager can do - not just for reviews, but for the entire employment relationship - is to keep a simple log of notable moments throughout the year.

This isn't about building a case against anyone. It's about having an accurate record that works in everyone's favor. When something goes well, you capture it. When something needs to be addressed, you note what happened and what was said. When patterns emerge, you can see them clearly instead of trying to reconstruct them from memory six months later.

Some managers do this in a shared drive. Some keep a notebook. Some send themselves a quick email after a meaningful conversation. The format doesn't matter; the habit does.

If you start now - even midway through the year - you'll be in a completely different position the next time review season comes around.

Pause-Consider-Act in performance reviews

In The Manager Method, I give you the Pause-Consider-Act framework for any situation as a people manager. You can (and should) use it for performance reviews. Before you finalize a review, Pause - step back from the review you wrote and read it again, but this time from your employee's perspective. What are they going to feel when they hear this? Where might they push back? Where might they be surprised?

Then Consider - is there anything that needs more specifics, added context or a clearer path forward? Act means you take the time to add those in or edit the language to make sure that the review will feel fair - not just to you from your perspective in delivering it, but to the team member who's receiving it.

A note on the conversation itself

Writing the review is only half of it. The conversation is where the review either means something or falls flat.

A few things worth keeping in mind before you sit down with your employee. Read through the full review before the meeting - out loud if you can - so you take in what you wrote and have an actual conversation. Nobody wants to feel like they're being read to. Know the key points you want to land and make sure you're not burying the most important feedback between two compliments.

If pay is part of the conversation - raise, freeze or anything in between - know what you're going to say before you walk in. "It's out of my hands" is one of the most damaging things a manager can say in a review conversation. Even if the decision wasn't yours, how you explain it matters. If you're not sure how to frame it, talk to HR beforehand.

And leave room for the employee to respond, including to ask questions. A performance review truly should be a conversation, not a presentation. Some of the most important things you'll learn about your team come from what they say in that room.

The bottom line

Performance reviews don't have to be dreaded - by you or by your team. When they're done well, they're one of the most valuable tools a manager has. They create clarity, recognize real contributions, address real problems and build the kind of trust that makes everything else easier.

The managers who do them well aren't necessarily the most experienced or the most polished. They're the ones who take it seriously, prepare before they write, and treat the review as the important document it actually is.

Performance management - from the feedback you give week to week all the way through the formal review - is one of the most important things managers are responsible for. If you want to build those skills from the ground up, Manager 101 covers all of it. Check it out for yourself or explore for the managers on your team at managermethod.com/manager-101.