In this lesson I've pulled together the 5 key mistakes that have the biggest impact on how well performance reviews work in an organization.

Following the principle that if you try to tackle everything at once, you usually don't do any of it properly, I suggest starting with exactly these five points. Make sure they're well designed and in place at your company, because they largely determine whether performance reviews will be a waste of time or a real lever for growing the organization.

No link between the process and the company's strategic goals

Failing to connect the process to the company's strategic goals is the mistake that turns performance reviews into "a conversation about the employee" instead of a tool for running the business.

When the process isn't tied to strategic goals, managers start assessing whatever happens to be in front of them: a general impression, recent wins, recent slip-ups, or whoever is most visible. The problem is that this doesn't always show whether a given person is genuinely helping the company deliver its most important goals.

An employee can be very busy, well-liked, and engaged, but if their work doesn't support the company's current priorities, the organization is paying for activity that doesn't move the business forward.

In practice, this means personnel decisions are still made on gut feel, managers assess by their own standards, and employees don't always know what really matters. In the end the company has plenty of conversations but little concrete data to inform decisions about promotions, raises, development, or team changes.

The hidden costs are very real: time spent on a process that leads nowhere, effort put into topics that are interesting but not strategic, promotions handed out for visibility rather than real contribution, frustrated people, and blurred accountability.

How to avoid it

Don't start with the form, the scale, or the review questions. Start by answering the question: which company goals is this process meant to support, and what decisions should come out of it?

Only then translate the strategy into team goals, individual goals, review criteria, and the questions on the form.

If you feel this piece isn't well organized yet, go back to Lesson 2, where we cover organizational readiness, the CEO's role, and cascading goals, and to Lesson 6, where I show how to set employee goals that you can actually assess a few months down the line.

Treating performance reviews as a one-off event on the calendar

If the process only comes alive once a year, and you try to fit everything into a single meeting:

- summing up results,

- discussing difficult topics,

- planning development,

- going over the employee's expectations,

- and sometimes pay and personnel decisions too.

Then there's a good chance the process has been treated as a one-off event.

In practice, this means managers try to reconstruct several months of working together from memory. So they start relying on what's most recent, most emotional, or most visible. The employee, in turn, may be caught off guard by the feedback, because they're hearing about something for the first time during the review, instead of getting a signal earlier, while there was still time to change course.

Hidden costs: the company loses the chance to react sooner, because problems only get discussed once they've already grown.

How to avoid it

Don't treat the performance review as a single meeting. Treat it as part of an entire management cycle: ongoing feedback, regular 1:1s, quick goal check-ins, and only then the bigger wrap-up of the period.

A performance review should be a summary of what the company has been talking about over the past few months, not the first moment an employee hears what's working and what needs to change.

You'll find the details on how to avoid this mistake in Lesson 10, where we cover building an annual review cycle for a company of 30-50 people, and in Lesson 11, where I show how to turn conclusions from the review into concrete action.

Expecting managers to run reviews without any preparation

If managers just get a form, a deadline, and a message that says "go run your reviews," they very often do it their own way. One will prepare specific examples, another will show up with a general impression, a third will dodge the hard topics, and a fourth will say everything too bluntly and shut the employee down.

In practice, this means employees go through completely different experiences within the same process and the same organization. One person leaves the conversation with a clear direction, another with a sense of unfairness, a third with vague generalities, and a fourth with tension that no one deals with afterward.

For the organization, the hidden costs are avoided difficult topics, conflicts after the conversations, and personnel decisions based more on the manager's style than on facts. This often leads to higher turnover and burnout among employees, and that translates into very real, sizeable costs, because replacing an employee, according to various sources, runs anywhere from 33 to as much as 200% of that employee's annual salary.

How to avoid it

Don't assume a manager "should just know" how to run a review conversation. It's a specific skill that has to be learned.

Before the process starts, managers should know:

• what the goal of the conversation is,
• how to prepare facts and examples,
• how to separate assessing the work from assessing the person,
• how to talk about difficult things without attacking,
• how to respond to emotions, resistance, and disagreement,
• how to close the conversation with concrete agreements.

If you feel your managers don't yet share a common standard for running these conversations, go back to Lesson 7, where we cover preparing managers for performance review conversations, and to Lesson 8, where I show how to run the review process in practice, step by step.

Ending performance review meetings on vague conclusions

This is the mistake that keeps even a good conversation from turning into real change in the company.

A meeting can be calm, substantive, and genuinely needed, but if it ends with phrases like "improve communication," "be more independent," "plan work better," or "get more involved," then nothing has actually been agreed yet. There are only good intentions.

In practice, this means that a few weeks later no one knows what exactly was supposed to happen. The manager assumes the employee got the point. The employee assumes they're "supposed to improve something," but doesn't know how the company will tell that things are better. So at the next review, you come back to the same problems.

The hidden costs show up as hours burned on a process that produces no results. Recurring problems, frustration on both sides, and eroding trust in the whole process. Employees quickly learn that reviews end in a conversation, but not in change.

How to avoid it

Every conversation should end with something concrete. Naming an area for improvement isn't enough. You need to agree on:

• what exactly should change,
• who is responsible for it,
• by when,
• how you'll know it's working,
• when you'll revisit the topic.

If your reviews leave behind plenty of general conclusions but few actions, go back to Lesson 9, where we cover documenting the agreements made after a review, and to Lesson 11, where I show how to turn post-review conclusions into a concrete action plan.

Building stress and tension around performance reviews

Because of this, performance reviews start to feel like control, a threat, or "putting a person on trial," instead of a conversation about work, development, and where things go next.

This most often happens when the process is poorly communicated from the very start. Employees don't know why the company runs reviews, what will be assessed, who will see the results, and what decisions might come out of it. In that situation, people fill in the blanks with the worst-case scenarios themselves: "is this about raises?", "will someone compare me to others?", "if I'm honest, will it be used against me?".

And that's when, more often than not, defensiveness shows up instead of an honest conversation. Employees play it safe, avoid difficult topics, don't admit to problems, and try to come across as well as possible. Managers, in turn, often tense up before the conversation, put off tough messages, or soften them so much that in the end no one knows what it was really about.

Less honesty, weaker data for decisions, more guesswork, more resistance to the process, and declining trust in managers and the organization - these are just some of the costs that can appear when this mistake creeps into the review process.

How to avoid it

Take care of the communication before the forms and meetings start. Employees should know:

• why the company is rolling out reviews,
• what will be assessed and what won't,
• whether and how reviews connect to pay,
• who will have access to the information,
• how to prepare for the conversation,
• what will happen after the meeting.

Most important: clearly separate assessing the work from assessing the person. It's not about "what someone is like," but about how they deliver on agreed goals, responsibilities, and the way they work with others.

If you feel reviews might create tension at your company, go back to Lesson 3, where we cover communicating the rollout of the process, and to Lesson 7, where I show how managers can run conversations in a way that's specific without attacking the employee.

To wrap up

A good performance review isn't about the company filling out a form once a year and holding a round of meetings. It's about the organization being able to talk regularly about goals, accountability, results, collaboration, and development - in a way that makes those conversations lead to better decisions.

So before your next round of reviews, ask yourself 5 simple questions:

👉 Does our review process genuinely support the company's strategic goals?

👉 Are reviews part of an annual cycle rather than a one-off event?

👉 Do managers know how to prepare for and run a good conversation?

👉 Do meetings leave behind concrete agreements, not just general conclusions?

👉 Do employees understand what reviews are for and not see them as a threat?

If even one of these questions raises any doubt, that's exactly where it's worth starting to improve the process.

The point isn't to build a perfect system right away. The point is to stop burning people's time on a process that gives the organization no real value.

Performance reviews make sense when they help the company work more effectively: make better decisions, strengthen accountability, develop people, and respond to problems faster.