A performance review isn't a standalone event in the calendar. It's a summary of what's been happening over the past several months – the 1:1s, the ongoing feedback, the work on goals, the day-to-day collaboration. When those things are happening consistently, the review conversation isn't difficult or surprising. It's a calm stocktake and a discussion about what comes next.

Each of the four areas covered in the review should be looked at from two angles simultaneously:

1. The organisation's perspective – what the company actually needs to deliver on its goals. Is this person's work moving the team, the projects, and the company forward? Are agreed goals being met, on time, at the right quality? Does the way they work support the strategy or get in the way of it?
2. The employee's perspective – what they need to grow and contribute effectively. What skills are worth developing? What do they need from their manager or the organisation? What will help them handle current and future challenges better?

A good review holds both of these in the same conversation. It's neither a dry results audit nor a loose development chat.

In this module, I want to walk through four areas that make a review useful both for the business and for the people involved. Understanding these four areas is also the foundation for designing the review process itself and choosing the right questions for your forms.

Area 1: Goals and results

This area is about what was actually delivered during the period. It covers progress against agreed goals, the quality of the output, whether things were done on time, and the real impact of the person's work on the team and the company.

This is the only part of a review that gives both sides a shared reference point. Goals and results are something you can talk about concretely – no guesswork, no interpretation, no "I had the impression that..." If this area gets skipped or treated as an afterthought, the rest of the conversation becomes subjective and hard to defend.

Start here, and focus on one question: what did we agree on, and what actually happened?

What works well:

• Go back to the goals that were set at the start of the period. That keeps the conversation honest and grounded in what both sides committed to.
• Anchor everything in facts: numbers, deadlines, specific examples. It reduces emotion and shortens the meeting.
• Separate the result from the context in which it was achieved. The same outcome can mean very different things depending on the circumstances.
• Talk about impact, not just completion. Ticking off a task isn't the same as creating value for the team and the company.
• Ask the employee to assess their own results first. It shows you how they understand their responsibilities and priorities.
• Acknowledge what was delivered – clearly and specifically. When people feel their work isn't seen, motivation drops. If no one notices what I do, why push so hard?
• If something didn't go well, focus on reasons and lessons rather than staying in the past. The point of the conversation is what to do differently going forward, not a postmortem.
• Check whether the goals stayed relevant throughout the period. If priorities shifted but the goals didn't, that's not the employee's problem.

What to avoid:

• Don't evaluate based on gut feeling or only the last few weeks. That leads to unfair conclusions and frustration.
• Avoid vague statements like "it was fine" or "could have been better." The employee doesn't know what specifically was fine or what needs to change.
• Don't hold people accountable for goals that were never clearly defined or that were outside their control. That's a fast way to erode trust in the whole process.
• Don't mix results with character or intentions. That triggers defensiveness, not accountability.
• Don't avoid difficult topics to "keep the atmosphere good." Unaddressed issues will come back in the next period and do more damage.

When this first area is handled well, the rest of the conversation gets easier. Once the facts are named and understood by both sides, moving to behaviours, collaboration, and development becomes more natural.

Area 2: Behaviours, values, and collaboration

This area is about how someone works day to day – whether their approach is consistent with the company's values and culture, and what effect it has on the people around them.

Results can be delivered in very different ways. That's exactly why this area matters. It's the everyday behaviours, decisions, and communication patterns that build your actual culture – not what's written on the website or in the company deck.

The same goal can be reached by taking ownership, flagging risks early, and caring about quality. Or by cutting corners, shifting blame onto others, and scrambling at the last minute. The goal gets done either way. The consequences for the team, the collaboration, and the company are entirely different.

So this area isn't about whether someone hit their targets – that was Area 1. It's about how they got there, and whether that approach is consistent with the values and culture the company wants to strengthen.

The best starting point is the employee's own behaviour and attitudes: how they make decisions, how they respond to problems and mistakes, whether they take ownership, whether their actions match the company's values. Only then move to the effects – how that approach affected collaboration, communication, team dynamics, and shared goals.

This keeps the conversation clear, specific, and psychologically safer. You're not mixing causes and consequences, which makes it easier to reach useful conclusions – both for working with that individual and for building culture across the organisation.

What works well:

• Ground the conversation in specific situations from the past months. "I remember that..." isn't enough. "In project X, you took responsibility for the decision despite incomplete information – that was consistent with how we think about ownership" is.
• Name the behaviours you want to reinforce. Don't assume they're obvious. Say them out loud: "The fact that you flagged the risk two weeks early gave the team time to respond. That's exactly the approach we want."
• Separate how someone acts from who they are. You're reviewing the work, not the person. Instead of "you avoid responsibility," say "in that situation, the decision was delayed and the team waited two days without any update."
• Only reference values that actually function in the company. Bringing up "dead values" – ones that exist on paper but not in practice – leads to frustration rather than insight.
• Distinguish between conflict and how it's being handled. Disagreement is natural and often healthy. Raised voices, verbal aggression, and talking over each other aren't. "The disagreement itself was valid, but the way the conversation escalated stopped the team's work for several hours."
• Check whether the employee sees their own behaviour the same way you do. Differences in perception are often the main source of misunderstanding. "How do you see your own reactions in those situations? What drove that response?"

What to avoid:

• Don't label – describe. Labels shut conversations down. Instead of "you have zero engagement," say "in three situations, the task came back incomplete and past the deadline."
• Don't evaluate intentions, only actions. You don't know what someone "meant." Instead of "you couldn't be bothered," say "the task was put aside without any update to the team."
• Don't sweep tensions under the rug because results are being delivered. That's always a delayed fuse. "The numbers are there, but the tension between you and the team means people are avoiding topics instead of resolving them. That slows things down and it will keep coming back."
• Don't hold one person accountable for systemic issues. A lack of organisational decision-making isn't the same as an individual communication problem.

Including this area in review conversations means you're building culture at the level of daily behaviour – not as a strategy document. It's where you make explicit what approaches are valued and what approaches, even when they produce results, aren't sustainable. This is often where the biggest "aha" moments happen on both sides.

Area 3: The employee's perspective and their experience of the organisation

This area is about how the employee experiences working with the company, the team, their manager, and the organisation as a whole. It's the moment when you hand over the floor and check what, from their perspective, supports effective work – and what gets in the way.

The goal here isn't to defend every decision the company has made or explain everything away. Treat it as gathering information that will help you understand the situation better and make smarter decisions going forward.

What works well:

• Give the employee space to speak freely. Open questions help: "How would you describe your experience of working with the team and the company over this period?"
• Ask about both what's working and what isn't. You need the full picture. "What helps you do your best work, and what gets in the way most?"
• Ask for specific situations, not general opinions. That makes the real issues easier to understand. "Can you give me an example of a situation where you felt you lacked support or clarity?"
• Treat the employee's feedback as information, not a verdict on the company. Your goal is to understand their perspective, not to debate it.
• Check what's actually within the company's control and what isn't. Separate things you can act on from those that require broader decisions.

What to avoid:

• Don't defend or explain away every point the employee raises. That closes the conversation and discourages honesty.
• Don't dismiss how someone feels. Everyone has the right to experience a situation in their own way. Instead of "others don't feel that way," try "I hear that. Let's understand where that's coming from and whether there's something we can do about it."
• Don't make promises you haven't actually checked are deliverable. A few empty commitments can undermine trust in the whole process.
• Don't try to solve every problem immediately. This stage is for gathering perspective, not making instant decisions.

This area shows you what the collaboration looks like from inside – and often surfaces barriers that aren't visible from the manager's position. Handled well, it reinforces a sense of partnership and means that subsequent development decisions are grounded in reality, not assumptions.

Area 4: Development and the future

This is where you bring together everything from the conversation and agree on what actually happens next. You talk about where the employee wants to develop, what competencies the company will need in the next phase, and what role this person wants to play in that. It's also the space to find out which directions genuinely interest and motivate them.

This is where concrete decisions get made: scope of responsibility, priorities for the next period, and what both sides are actually committing to.

This area isn't about building a list of trendy training courses to tick off. It's not about setting ambitious goals that have no connection to reality. It's about clear agreements on what comes next – grounded in what the company is actually doing and where it's going.

What works well:

• Summarise the conversation before proposing anything. Don't lead with your ready-made solutions. Ask what the employee sees as the next steps first – you'll learn a lot about how they understand their situation. Instead of "from next month we're changing X and you're going on training Y, any questions?" try "let's summarise what we've agreed today. How do you see the next steps after this conversation?"
• Connect development to company goals. That's how you make sure people's growth is aligned with where the organisation is heading. "In the next half-year we're going to need someone who can take more ownership of X. Is that a direction that interests you?"
• Tie development to concrete responsibility, not abstract learning. People develop fastest when they can put new things into practice immediately. Instead of "you should work on communication," try "in the next period, I'd like you to run the team status meetings. What would you need to develop to do that well?"
• Pick one or two development areas, not everything at once. Too many commitments usually means nothing happens. "Let's focus on just two things: making more decisions independently and communicating risks earlier."
• Be specific about what changes after this conversation. Development without change in daily work is just talk. "From next month, you take over X. I step back as the decision point in that area."
• Agree on how you'll both know the development is actually happening. "If after three months decisions are being made without escalating to me, we'll call that a success."

What to avoid:

• ^Don't end with vague conclusions like "we'll see in six months." That's a conversation neither side will come back to.
• Don't promise promotions or changes without a real plan. It builds false expectations and leads to frustration.
• Don't close the meeting without specific agreements. If nothing concrete is decided, the review ends the moment everyone leaves the room.

This area is what lets both people walk out with a clear direction – not just a summary of the past. Vague declarations get replaced with concrete commitments that can actually be acted on. That's what turns a performance review from a closed chapter into a starting point for what comes next.

To close

A good performance review brings a period of collaboration into focus and gives both sides a clear direction for what follows.

Working through four areas from two angles – the organisation's and the employee's: goals and results, behaviours and values and collaboration, the employee's experience of the organisation, and development and the future.

This keeps the conversation structured and prevents improvisation from taking over. The result is a meeting that's shorter, more concrete, and actually useful.