A tough performance review is one of the hardest things to write well. Too vague, and it's useless. Too harsh, and it reads like a takedown. Too one-sided, and even a valid assessment can become a debate.

Most managers know a difficult review needs to be delivered. What's less obvious is why it matters so much to do it right - and what "right" actually looks like.

Watch: HR coaches a manager through a performance review that needs work - before it gets delivered.

Even when you think of someone as a "problem employee," that employee may not actually know there's a problem. Not because they're oblivious, but because you may not have said it clearly enough, often enough or in a way that they actually heard. A critical review isn't just paperwork. For many employees, it's the first time the situation feels real and documented. That's a lot to absorb. So how you write it - and how you frame it - has a significant impact on what happens next.

The goal isn't to be nice for the sake of being nice. It's to be effective. Including the four aspects I mention in the video above: honest, specific, fair and not a surprise. If any of those four are missing, the review stops doing its job.

Here's how to use Pause-Consider-Act to get all four right.

Pause: What Are You Actually Trying to Accomplish?

Before you write a single word of a critical review, pause and get clear on why you're writing it in the first place.

It's not to build a paper trail, or to vent about a frustrating year. It's to help this person understand where their performance has fallen short, what the impact has been and what needs to change - specifically enough that they can actually do something about it.

That reframe matters. A review written just to document problems looks different from a review written to create real change. The language and tone - both on the page and in how you deliver it - aren’t the same. And the reactions - and results - will be different, too.

Also pause to ask: Is this going to be a surprise? Because it shouldn't be. If the feedback in the review is the first time this employee is hearing it - or if they could reasonably argue they've never been clearly told - that's a problem before you even get to the conversation. A critical review should confirm and formalize feedback that's already been given, not introduce it for the first time.

If you're not sure whether your employee knows the concerns are serious enough to show up in their review, that's worth thinking through before you finalize anything.

Consider: What Does This Look Like From Their Side?

This is the step most managers skip, and it's where a lot of reviews go sideways.

Once you've drafted a review, step away from it. Then come back and read it as if you're the person receiving it. Not just "would this be hard to hear?" - but more specifically: "Does this make sense? Is it fair? Is there anything I could reasonably push back on? Is there anything missing that would make me feel like I'm not getting the full picture?"

A few common issues that you may only catch by rereading:

Vague language. "Not detail-oriented" or "needs to improve communication" aren't feedback - they're conclusions without evidence. They don't tell the employee what actually happened, nor give them anything to change. For every general statement in a critical review, attach a specific example: what happened, when and what the impact was. That's the feedback, and important to make it understandable and actionable.

Only covering what's gone wrong recently. Recency bias is real, and it cuts both ways. If your review reads like twelve months of nothing but problems, but the employee can point to solid work earlier in the year that isn't mentioned anywhere, it starts to feel like a setup. That doesn't mean you soften the critical feedback - it means you give a complete picture. Even in a tough review, acknowledging what someone did well isn't being soft. It's being accurate. It also makes the critical feedback land better, because they can see you're evaluating them honestly rather than just listing problems.

Feedback the employee could genuinely dispute. Think about whether there's anything in the review they'd argue wasn't their fault, wasn't clearly communicated to them, or doesn't reflect what actually happened. You don't have to agree with them - but if you can anticipate the objection, you can address it directly in the review rather than being blindsided in the conversation.

Also worth considering: Did this person course-correct on anything this year? If they made mistakes and adjusted, that's worth noting (and considering how you can call that out positively, especially if your organizational values include things like Resilience or Courage). How someone responds to feedback is itself a data point - and a review that ignores growth can feel just as unfair as one that ignores problems.

Act: Write the Review That Creates Change

Now write (or rewrite) with all of that in mind. The goal is a review that's honest, specific, fair and builds a real path forward.

That means:

Specific examples for every critical point. Not "missed deadlines" but "the quarterly report was submitted three days late in March and again in September, which created delays for the finance team in both cycles." Not "communication issues" but "in three separate team meetings this quarter, feedback from colleagues was either dismissed or not acknowledged, which has affected how team members feel about raising concerns."

The full picture. Include what went well, even if the overall review is difficult. If there's genuinely nothing positive to include, ask yourself whether this review is the right tool for where things stand - or whether a more direct performance conversation needs to happen first.

A clear forward-looking section. What does success look like from here? What specifically does the employee need to do differently, and by when? What support will you provide? This section is the difference between a review that closes a chapter and one that actually opens a path forward.

Language that's direct without being punitive. There's a difference between "your performance has been unacceptable" and "these specific things need to change in order for you to be successful in this role." One shuts the conversation down. The other keeps it open - and it's more legally defensible, too.

One More Thing: Deliver It, Don't Just Hand It Over

A tough review is a conversation, not a document you send and hope lands well. Once you've written it, think about how you'll deliver it. What tone will you set? What questions will you ask to make sure they understand - and to give them a chance to respond? What's the plan for following up?

The written review matters, and the conversation around it matters just as much.

If you want to see what the coaching version of this looks like in action - including how HR might walk a manager through a review that needs work before it gets delivered - watch the video above. It's a quick roleplay that covers a lot of what I'm talking about here.

The Bottom Line

Reframe a critical performance review as a constructive one. A review done well is honest, specific, fair and not a surprise. It gives the employee a real picture of where things stand - and a real path forward. That's not just good management - it's the kind of leadership that can actually change what happens next.

For Managers: If you're navigating performance conversations - whether that's a tough review, a coaching conversation, or figuring out how to document performance effectively - Manager 101 walks you through all of it with practical tools and language you can actually use. Check it out at managermethod.com/manager-101.

For HR Leaders: If your managers need real support going into review conversations - not just policies, but the actual skills - our Leadership Platform is built for exactly that. Visit managermethod.com to learn more and set up a call.

Next week: what to say - and do - after a tough review conversation. Because what happens in the first few weeks after can matter just as much as the review itself.