If you want to prepare an annual review well, you usually start too late. The pattern is familiar: in November an invitation from HR lands in your inbox, the date gets closer, and the evening before you sit in front of an empty form trying to reconstruct twelve months from memory. What comes out is mostly what happened in the last six weeks. That is human, but it is unfair to the person sitting across from you.
In this guide I show you how I would prepare an annual review today: with a four-week schedule, a 60-minute agenda, questions for each phase and a look at typical rating errors. The article is for team leads and managers doing this for the first time, and for anyone who feels their annual reviews are more of a mandatory appointment than a real benefit.
In short
A good annual review sums up what you already discussed during the year and mainly looks ahead. The most important preparation is collecting evidence from the whole year instead of judging from memory. The biggest pitfall is critical feedback that comes up for the first time in the meeting itself.
What you will learn in this article
- How to prepare an annual review over four weeks without stress
- A 60-minute agenda with questions for each phase
- Which rating errors you will meet and what helps against them
- How to discuss critical feedback and disagreement fairly
What is an annual review, and what is it not?
An annual review (also called a performance review, appraisal or development conversation) is a planned meeting between you and someone on your team that looks back at your collaboration once a year and also looks forward. It has three jobs: putting the past year into perspective together, talking about growth and agreeing on concrete next steps for the coming months. Many companies provide an HR form, sometimes with a rating scale.
What it is not: the only place for feedback. Gallup reports that only 14 percent of employees strongly agree that their performance reviews inspire them to improve. At the same time, nearly half say they get feedback from their manager a few times a year or less. These two numbers belong together. If the annual review is the only occasion to talk about performance, it carries a load no single meeting can carry.
That is why I see the annual review as a summary. Any feedback that comes up there should be something the person has heard before, for example in your recurring one-on-ones. Ideally, only the agreements for the coming year are new.
The legal framework in Germany, briefly
If you lead a team in Germany, you should know a few points from the Works Constitution Act (BetrVG), even if you do not work in HR. Under Section 82(2) BetrVG, employees can ask to discuss their performance assessment and their career development options within the company. They may bring a member of the works council, who must keep the content confidential unless the employee releases them from that duty.
In addition, under Section 94(2) BetrVG, setting up general assessment principles requires the works council's consent. In practice this means: do not invent your own rating scale or form if your company has an agreed process. Ask HR what applies and stick to it. Outside Germany the rules differ. This is not legal advice, just a pointer to where you should ask for details.
Prepare an annual review in four weeks
Four weeks sounds like a lot. If you prepare an annual review this way, you only need about two to three hours per person, spread over a month. The benefit of spreading it out: you have time to look up evidence and rethink your assessment instead of getting locked into one direction the night before.
Four weeks before: date and invitation
Plan 60 minutes, better 75, so nobody watches the clock. Choose a quiet room or, when remote, a slot without a meeting right afterwards. In the invitation, say what it is about and how the person can prepare. Here is a sample text you can adapt:
“Hi Alex, our annual review is in four weeks. I’d like to look back at the year with you, talk about your growth and agree together on what we focus on next year. Please think about this beforehand: What are you proud of? What slowed you down? What would you like to learn? You’ll get my notes a week in advance, so there are no surprises.”
The last sentence matters most. It takes the fear out of the meeting and commits you to being ready on time.
Three weeks before: collect evidence from the whole year
To prepare an annual review fairly, you now go through the year month by month. Good sources are your one-on-one notes, the goals from last year’s review, completed projects, feedback from others and your calendar. The calendar is especially helpful for remembering: Which workshops did the person facilitate, which incidents were they involved in, whom did they onboard?
For each point, write down an observation, not a judgment. “Took over onboarding two new colleagues in March and wrote a checklist for it” is an observation. “Is very helpful” is a judgment. You can derive a judgment from observations later, but not the other way round. If you find nothing at all for a three-month period, that is an insight too, and it is about your own leadership.
If you want input from colleagues, tell the person in advance and ask specifically for concrete situations. Anonymous blanket verdicts without examples do not help in the meeting, because nobody can respond to them in a meaningful way.
One week before: key messages and sharing your notes
Condense your notes into three key messages at most: what went particularly well, where you see room to grow and which direction you suggest for next year. Everything else is evidence you can bring up in the meeting if needed.
Then send your notes to the person. Many managers hesitate here because they fear it gives the conversation away. I see it differently: someone who can read beforehand responds more thoughtfully, and you spend the time thinking together instead of processing. If there is a form with a rating scale, the same applies to your preliminary assessment, as long as your company’s process allows it.
On the day: ten quiet minutes
Block ten minutes before the meeting. Read your key messages once more, read the person’s preparation if they sent you anything, and put away the laptop with all its open chats. That sounds trivial. Still, people notice very clearly whether your head is still in the last meeting.
Rating errors you will meet in an annual review
Rating errors are systematic biases that affect how we judge other people. Nobody is immune to them, not even with good intentions. It helps to know the most common ones and have a countermeasure ready for each.
| Error | What happens | Countermeasure |
|---|---|---|
| Recency effect | The last few weeks weigh more than the rest of the year. | Collect evidence month by month, not backwards from the end. |
| Halo effect | One strong trait outshines everything else, for better or worse. | Assess each topic separately with its own evidence. |
| Leniency or severity | You systematically rate everyone too high or too low. | Put your assessments for the whole team side by side. |
| Central tendency | Out of caution, everything ends up in the middle. | Be able to name a concrete situation for every rating. |
| Projection | People who work like you seem better. | Ask: Would I rate this result the same way for someone else? |
Common rating errors and what you can do about them
I consider the recency effect the most important one, because it is so inconspicuous. A difficult release in October can completely overshadow a strong first half of the year without you noticing. Collecting evidence as described in the previous section is therefore your most important tool against this effect, even if it feels like bureaucracy.
Annual review agenda: 60 minutes in five phases
A fixed agenda gives both sides confidence. It also makes sure the look ahead does not get squeezed into the last five minutes. I would split the meeting into five phases:
Agenda for a 60-minute annual review
Opening (5 minutes)
Briefly explain how the meeting works and that it ends with agreements you both write down. Ask whether the person definitely wants to discuss something specific, and add it to the agenda.
Looking back from their perspective (15 minutes)
The person speaks first. This is not a courtesy ritual. If you judge first, everything that follows aligns with your judgment. If they talk first, you learn what mattered to them, and often things you did not notice at all.
Your view (15 minutes)
Now you bring in your three key messages, each with one or two pieces of evidence. Start where you agree with the person and add what else you noticed. Critical points belong here too, clear and concrete, not hidden between two compliments.
Growth (15 minutes)
For me, this is the most valuable part. Where does the person want to grow: deeper technically, broader, towards leadership or architecture? Which of that fits what the team needs? Open questions help more than suggestions here. By the way, a stay interview during the year is a good complement, because it asks the same questions without the pressure of a rating.
Agreements (10 minutes)
Write down two or three agreements, not ten. Each one needs a recognizable outcome and support from you. “Take on more responsibility” is not an agreement. “Facilitates the retrospective from February, and I give feedback after the first two sessions” is. Write the agreements down together at the end and decide when you will revisit them in your one-on-ones, for example once a quarter.
Questions to prepare an annual review
You do not have to ask every question. Pick two or three per phase that suit the person.
Questions for looking back
- Which result from this year are you most proud of?
- What cost you the most energy, and why?
- Where would you have liked more support, including from me?
- What did you learn this year that you could not do a year ago?
Questions about growth
- Which tasks would you like to do more often, and which less often?
- Where do you see yourself in two years, and what would need to happen for that?
- Which skill would help you most next year?
- Is there a topic in the team you would like to take ownership of?
Questions about you as a manager
- What should I keep doing next year?
- What should I do differently so you can work better?
- Was there a situation where you would have wished for a different decision from me?
That last group is often forgotten. Yet the annual review is one of the few occasions when people dare to tell their manager something critical. I described how to receive that kind of feedback well in the article on asking for feedback as a manager.
Critical feedback in the annual review
The most important rule is: no surprises. If you say for the first time in the annual review that something has bothered you since March, the person rightly feels you took away eight months in which they could have changed course. If you notice such a point while preparing, raise it in a one-on-one first and then include it in the annual review as a shared look back.
For the wording, the SBI model from the Center for Creative Leadership helps. SBI stands for Situation, Behavior, Impact. You describe a concrete situation, the observable behavior and the effect on you or the team. In addition, you ask about the person’s intent, because there is often a gap between what was meant and how it landed. An example: “In last week’s planning you interrupted Kim’s estimate twice. After that, Kim didn’t say anything until the end. What mattered to you in that moment?” There is more on this in the guide giving feedback that lands.
When you cannot agree
Disagreement is not failure. It shows that someone is speaking honestly. Listen to the person’s view completely, ask for evidence you do not know about, and check whether you need to adjust your assessment. If you still end up with different views, write both down. A sentence like “Alex considers the operations responsibility fulfilled, I still see gaps in the handover” is more honest than a compromise neither of you shares. If needed, schedule a second meeting instead of rushing the conversation to an end.
Should you discuss salary in the annual review?
In many companies, the annual review and the salary round are linked. My position is clear: if at all possible, separate them in time. As soon as money is on the table, a development conversation becomes a negotiation. Then nobody talks openly about weaknesses or learning goals anymore, because every sentence might affect their pay.
If your company does not allow that, address it openly: “We’ll also talk about salary today, and we’ll do that at the end in a separate part.” That way at least the growth part stays free of it.
And if you are sitting on the other side of the table yourself: I describe how to prepare for your performance review as a team member in a separate guide.
My take
There are good arguments for abolishing the yearly conversation entirely. Gallup describes, for example, that employees who get weekly feedback are much more likely to say they receive meaningful feedback and feel motivated than those with annual feedback. I share the criticism of the annual review as the only feedback channel. Still, I would not abolish it.
Here is why: day to day, one-on-ones mostly look at the next few weeks. Stepping back once a year to look at your collaboration from a distance has its own value, especially for growth. What matters is what happens before. An annual review is only as good as the twelve months of conversations it sums up. If you notice you can hardly prepare an annual review because you lack material, the solution is not a better form but more frequent conversations during the year.
FAQ
How long should an annual review take?
Plan 60 to 75 minutes. Shorter slots are usually only enough for looking back, and the growth part gets too little time.
How do I prepare for my annual review as an employee?
Note two or three results you are proud of, what slowed you down and what you want to learn. Bring concrete examples and think about what support you need from your manager.
Can a works council member attend the annual review in Germany?
Yes. Under Section 82(2) BetrVG, employees can bring a works council member when discussing their performance assessment and development. That member must keep the content confidential.
What is the difference between an annual review and a one-on-one?
A one-on-one happens regularly, often every one or two weeks, and deals with current topics. The annual review looks back at the entire collaboration once a year and sets agreements for growth.
Your next step
Check your calendar today: when are your annual reviews? Count back four weeks from each date and block 30 minutes there for collecting evidence. If you then adapt and send the invitation from above, you can prepare your next annual review better than most.
Over to you: What was the best annual review you have ever had, on either side of the table, and what made it so good?
Sources
- Section 82 BetrVG: employee’s right to be heard and to discuss (gesetze-im-internet.de, German)
- Section 94 BetrVG: personnel questionnaires, assessment principles (gesetze-im-internet.de, German)
- Gallup: More Harm Than Good: The Truth About Performance Reviews
- Center for Creative Leadership: Use Situation-Behavior-Impact (SBI) to Understand Intent
- Wikipedia: Beurteilungsfehler (rating errors, German)
This post was created with AI assistance.
👉 Next step: Preparing a first one-on-one? My question cheat sheet puts the best questions on one printable page.
📬 Stay updated: New articles on serverless, AI and leading tech teams via RSS, browser push or the weekly newsletter (in German).
Originally published on sascha-ms.de. More articles on serverless, AI in everyday development and leading tech teams: sascha-ms.de/en
