In my experience, it's rarely the process itself that creates resistance. It's how it gets communicated – rushed, without context, without answering the one question everyone actually has: why are we doing this?

That moment, more than anything else, determines whether the process sticks.

So before we get into tools and forms, let's talk about how to get the communication right.

Why people are afraid of performance reviews

There are many reasons, but I want to focus on one – because it has an outsized effect on whether the process takes hold, and because it's something you can directly control.

It comes down to the narrative that forms around performance reviews inside the company.

Reviews as an attack on self-worth

This narrative rarely gets built on purpose. It usually emerges unconsciously, through shortcuts and time pressure. But it's one of the main reasons performance reviews fail to deliver.

It forms when communication about reviews centres on personalised "you" language that employees hear as judgements of them as people:

• "Reviews will help us see how valuable you are to the team."
• "We'll be assessing your competencies."
• "Reviews will show us how good you are."

The intention is to talk about work. But employees can easily read these messages as a verdict on who they are – not a conversation about responsibilities, behaviours, or how they're approaching their tasks.

When a manager then can't distinguish between the work and the person, the review conversation starts to feel like a personal attack. The natural response is defensiveness: shutting down, over-explaining, withdrawing, or pushing back.

So what narrative do we want instead?

If the goal is development and delivering on company goals, the framing needs to shift entirely.

"A review isn't about who someone is. It's about whether the agreed areas of responsibility are being met."

That's a subtle distinction, but it's the one that matters.

Good performance review communication uses the language of work, process, and future direction – not labels. Examples:

• "In reviews, we look at how the agreed areas of responsibility are being delivered."
• "We talk about work outcomes, behaviours, and how people collaborate."
• "Reviews help us see what's working and where we can improve how we work together going forward."

Why this matters

When feedback is received as a judgement of a person rather than part of a learning process, it triggers a fear of failure and the need to defend one's self-worth. At that point, the review stops supporting development and starts blocking it.

Carol Dweck describes this mechanism in Mindset – showing how the way feedback is framed affects motivation, willingness to learn, and how people respond to challenges.

When a review is about "who you are" rather than "how you work," the employee isn't looking for ways to support the company's growth. They're looking for ways to protect their value in your eyes and their own.

The results are concrete: dishonesty in conversations, avoidance of accountability, declining engagement, and a review process that doesn't help the company move forward. The exact opposite of what you were hoping for.

Why people resist

Introducing a new process usually starts and ends with a brief announcement dropped into a company meeting or sent by email. Something like:

"Starting next month, we're rolling out a performance review process. HR will provide the tools and forms. You'll receive your review date with a week's notice."

It's worth pausing on why this kind of message almost always creates resistance – even when the decision to introduce reviews is the right one.

Any organisational change, even a rational and necessary one, triggers a natural adaptation process in people. And that process doesn't happen in a single moment. It unfolds over time.

That's why the communication and rollout of a new process needs to unfold over time too – in stages.

Kurt Lewin's change model describes this well. In practice it means: before you introduce a new process, you need to "unfreeze" the current way of thinking and working. You need to explain why the existing approach is no longer enough and where the need for change comes from. Only then comes the actual change – testing the new approach in practice. And at the end, the new way of working needs to be reinforced so it becomes a permanent part of how the company operates, not a one-off event.

Communication plays its most important role in that first stage – the unfreeze. It's what prepares the organisation and its teams for what comes next.

A five-step model for communicating change – applied to performance reviews

Now that we understand why people are afraid and where resistance comes from, let's get practical.

Here's a simple five-step model that takes teams from the first announcement through to genuine readiness to participate.

Step 1: I know

This is the moment employees first hear that the company is planning to introduce performance reviews.

The goal here isn't to explain the details or convince anyone of anything. It's to deliver a clear message about what's coming and when.

Before drafting this communication, answer these questions:

• Intention: What do we want to review in our company, and why? Can I explain it in one sentence?
• Reason for the decision: What has stopped working at this stage of the company, and what specific problems do we want to solve? What happens if we don't introduce this process now?
• Expected outcome: What should concretely change? How will we know we've achieved our goal?
• Next steps: What do we already know about the rollout timeline and what can we share now?
• Employee involvement: When and how will people be able to ask questions and have input into how the process is shaped?

Step 2: I understand – the why, the what, and the how

Employees now know reviews are coming. Questions start forming – some spoken aloud, others not:

• Do I have to take part?
• Will this affect my salary?
• Is it safer to keep quiet or to actively engage?

This is the moment when people are trying to make sense of what reviews mean for them personally. Without clear answers, speculation, rumour, and disengagement follow quickly.

The goal of this step is to defuse those doubts and make the process meaningful from the employee's perspective.

Questions to answer before drafting this communication:

• Employee perspective: What will actually change in their day-to-day work? What's in it for them?
• Safety: What will review conversations cover, and what definitely won't they cover? How do we separate a review of work from a judgement of the person? Who will have access to what's discussed?
• Consequences: Are reviews connected to pay or personnel decisions? If so, how? What happens if someone is going through a difficult period?
• Manager consistency: Do all managers understand the purpose of the process well enough to explain it to their teams? Do they have consistent answers to the hardest questions?
• Channels: Where and how will employees be able to ask questions and raise concerns as they come up?

Step 3: I want

Here the goal is to help employees answer for themselves: do I actually want to participate in this?

This is the hardest communication step, because it can't rely on clear messaging alone. It requires dialogue. Concerns surface. Questions come up. People bring experiences from previous companies. All of it needs to be heard.

Don't expect enthusiasm here. Acceptance and willingness to participate is the goal. Skipping this step almost always results in passive compliance – people ticking boxes instead of genuinely engaging.

Questions to answer:

• Space for concerns: What questions and worries are likely to come up? Are we prepared for the uncomfortable ones, not just the easy ones?
• Invitation to dialogue: In what format will we give people the chance to actually talk? Do we have the time and capacity to genuinely listen?
• Employee influence: Which parts of the process can employees realistically have input on? And how will we show that their input made a difference?
• Manager alignment: Are all managers speaking with one voice? Do they know how to respond to resistance, emotion, and disagreement?

Step 4: I can – practical preparation

This step is about inviting employees to get familiar with the process and the tools – and to give feedback on them.

Acceptance of the process isn't enough on its own here. Even the most sensible and well-received review process won't work if people – especially managers – don't feel equipped to run it.

The goal is to build confidence and get the organisation ready to act before the first conversations happen.

Questions to answer:

• Manager preparation: Do managers know how to run a developmental review conversation? Can they separate a review of work from a judgement of the person? Are they prepared for difficult emotions, pushback, or disagreement?
• A shared standard: Do all managers have a clear picture of what a review conversation looks like in this company? What's required, and what's flexible? What happens before, during, and after the conversation?
• Tools and process: Are all the tools ready? Can we explain clearly what they're for and how to use them – in language that doesn't require a technical background?
• Readiness: How much time will people have to prepare? Are we communicating that the goal is a useful start, not perfect execution?

Step 5: I'm ready – the signal to start

This is the final step before the first review conversations happen. The goal is to acknowledge the work that's gone into getting here and to confirm that nothing is standing in the way.

Questions to answer:

• Organisational readiness: Have all participants received the tools, instructions, and information they need? Are managers available and prepared? Who communicates the start – and when? Does the timing conflict with any major company event?
• Feedback: How will people be able to share their experience after the first conversations? Are there still outstanding concerns that need to be addressed?
• Consistency check: Is the communication from the CEO, HR, and managers aligned? Are contradictory messages circulating anywhere?

Who does what

In practice, roles blur and sometimes everything lands on one person. Here's what I've seen work best.

• CEO / Founder – responsible for the first and most important message. Their voice is what gives the whole process weight. They explain why the company is introducing reviews now and what the process is supposed to achieve at this stage of growth. That framing is what signals to employees that this is a real change, not an HR checkbox.
• HR – supports the preparation of communication and makes sure it stays consistent with company values and culture. HR helps the CEO and managers answer the hard questions and keeps everyone speaking from the same page. Since they own the process design, they also provide a lot of the practical information that the CEO and managers need to communicate clearly.
• Managers – they're closest to the people, which makes their role in communication critical. They're the ones fielding questions and emotions after the company-wide announcement. They're who employees turn to and ask "but what does this actually mean for me?" Their job is to reinforce the same message – not add their own interpretation to it.

In short: the CEO gives the process meaning, HR keeps communication consistent, and managers translate it into real conversations with their teams.

What this looks like in practice

These steps rarely happen in neat sequence. In practice, they overlap and get picked up by different people at different times.

Steps 1 and 2 usually happen together. The CEO announces the decision – typically at an all-hands or company meeting – explains why now, and what the company expects to achieve. Questions start coming in, some in the room, some afterwards. HR follows up with a short email, a Q&A document, or information about where to ask more.

Steps 2 and 3 move to team level. Managers have conversations in team meetings, in 1:1s, often in passing during the normal workday. Concerns come up, comparisons to previous companies surface, sometimes scepticism. This is dialogue, not a broadcast. HR supports it by gathering the most common questions and making sure answers stay consistent across the organisation.

Step 4 gets concrete. HR walks people through the process, the tools, the forms, the timeline. Managers are prepared to run the conversations. Employees know what to expect and what will be asked of them.

Step 5 is the signal to start – usually a simple message from a manager confirming dates, summarising the key points, and closing out any remaining questions.

The through-line: communication doesn't happen once. It's a process, extended over time, where different people take the lead at different stages. The goal isn't to follow the model perfectly. It's to know where your people are right now, and to give them what they need from communication at that specific moment.

To close

As you can see, communicating a performance review process takes several stages and involves a number of people, each with a specific role. To help you make sure you're ready for the first conversations, I've put together a short launch checklist.