Managers sit down for these conversations once or twice a year and try to remember what actually happened over the past several months. On top of that, it eats up a lot of their time and often delivers no business results.

In this lesson, I'll show you how to structure an annual review cycle in a company of 30-50 people so that it actually works in practice.

A feedback culture - the foundation of effective performance reviews

If feedback only shows up at review time in your company, the process doesn't stand a chance of working.

Why? Because you're trying to sum up 6 or 12 months of work based on memory, general impressions, and the last few weeks.

This is confirmed by what's known as the recency bias, which says we remember most vividly what happened recently. As a result, during performance reviews we judge people mainly through the lens of recent events rather than their entire period of work.

For years, Gallup has shown one thing very clearly: employees who get regular feedback are more engaged and perform better. A lack of ongoing feedback, on the other hand, creates chaos - people don't know whether they're doing a good job, what they need to improve, or what's really expected of them. The latest data from 2026 only confirms this - a full 51% of employees aren't clear on what's expected of them at work.

And here's the key point:

👉 a performance review shouldn't be the moment for "giving feedback"
👉 it should be the moment for summarizing it

Feedback as part of managing, not a one-off process

In a well-run company, feedback isn't a "big" event. It's a way of working. That means:

• the manager says what's working and what isn't as it happens
• the employee isn't caught off guard during the review
• the review conversation doesn't bring "new information" - it organizes what was already there

A real-life example:
You have a developer on your team who, for the past 3 months, hasn't been closing out tasks on time.

❌ If you only tell them about it at the annual review - it's too late. You've lost a year of the team's productivity. In that time, projects fall behind, other team members have to take over their tasks, and frustration builds - quietly, but steadily.

✔️ If you respond as it happens - you have a chance to correct it within 2 weeks. Clarify expectations, find the cause (priorities, a skills gap, being overloaded), and get back on track before the problem starts affecting the whole team.

And that's a real business difference.

How to build a feedback culture in a company of 30-50 people

The good news is that in a company this size, it's much simpler than in a large corporation. You don't need complicated tools. You need a few clear rules and consistency.

1. Set the standard: feedback is a natural part of work

Not as an "option" or a "nice extra," but as a normal part of a manager's job. Regular feedback is their responsibility - just like delivering results or working with the team.

👉 The manager has to lead by example - if they don't accept feedback themselves and don't initiate it, the team won't do it either.
👉 Feedback should flow in every direction - not just top-down, but also from employees to managers and between team members.
👉 It's worth actively encouraging people to share feedback - showing that it's safe and genuinely shapes how you work.

2. Anchor it to specific moments in the work

• "here and now" situations - short comments on the work
• 1:1s (e.g. every 2 weeks)
• a sprint / project wrap-up

3. Keep the format as simple as possible

Feedback doesn't have to mean a 20-minute conversation following the FUKO model (Facts-Feelings-Consequences-Expectations).

Often this is enough:
✔️ "This worked well, because…"
✔️ "It's worth improving X here, because it affects Y"

4. Make it safe

People need to feel that they won't face negative consequences for giving feedback - whether about the company or about the manager. It's just as important that they understand the manager's intent: feedback is meant to support growth, not to judge them as a person.

You'll find more on how to communicate performance reviews grounded in psychological safety in lesson 3.

If the first experiences are negative - the whole thing will die very quickly, and it'll be hard to turn around.

The manager's role in sustaining regular feedback

If a manager avoids difficult conversations, puts feedback off "for later," and only comes back to it at review time, in practice they lose control over what's happening in the team. Problems build up for months, productivity drops, and in the end it all piles into a single conversation.

The result?
👉 the employee is caught off guard, because no one flagged the problem earlier
👉 the conversation turns emotional instead of substantive
👉 decisions (about raises, promotions, or letting someone go) are hard to defend

And at that point it's no longer just a communication problem, but real business losses and hidden costs.

On the other hand, if a manager works on things as they come up, the situation looks completely different. Feedback is part of the everyday work with the team, so the review conversation isn't a "collision with reality" - it's a natural summary.

👉 the conversations are shorter and more focused
👉 the decisions are based on facts, not impressions
👉 people know where they stand and what's expected of them

And that's the moment when performance reviews start to make business sense, because they support decisions instead of getting in the way of them.

You'll find more on how to prepare managers to run performance reviews and give feedback in lesson 7.

How many performance reviews a year make sense?

In lesson 8 we talked about how to pick the right time to run performance reviews.

Now a natural follow-up question comes up: how many of these meetings should there even be over the course of a year?

Because in practice you'll come across all kinds of approaches - from one review a year, to semi-annual, all the way to quarterly conversations.

In my experience, a very simple setup works best.

It's a model built on three levels:

👉 once a year you pause for longer and make decisions
👉 once a quarter you check whether you're heading in the right direction
👉 day to day you work with people through feedback

And the key is that each of these meetings has a completely different role.

The annual review is the moment when you take the wide view.

Not just at the last few months, but at the entire year of work.
This is where decisions are made - about growth, pay, direction, sometimes about changes in the team. Depending on the goal you choose for your performance review process and how you design it.

This is a meeting meant to sum up a given period of time and make decisions.

And that's exactly why, in many companies, doing it more often doesn't make sense.
Because you don't have enough data to make big business decisions every few months.

Quarterly meetings serve a completely different function.

These shouldn't be "mini reviews," but meetings where you check in with the team and see whether what you agreed on is actually happening.

Goals should be transparent, and the meetings themselves - run as a team. That's not just a time-saver, but also a way to build shared ownership of delivering results.

It's the moment to answer a few simple questions:

• are the goals still relevant
• is anything drifting off course
• does anything need adjusting

It's the space to clarify expectations, shift priorities, and react quickly.

In my experience, it's exactly these conversations that make the biggest difference. You don't wait 12 months for a problem to grow - you respond while you can still change something.

And finally there's the thing that ties this whole system together, which I mentioned at the start of this lesson.

Everyday feedback.

Without it:

• the annual review will be a surprise
• the quarterly conversations will be disconnected from reality
• decisions will be based on impressions

And with it:

• people know where they stand
• managers have the data to make decisions
• the conversations are shorter and more focused

The most common mistake I see in companies? Trying to do everything at once. Feedback, evaluation, decisions, a development plan - all in one conversation, once a year.

The result is always similar:
❌ too many topics, too little time, a lot of emotion, and few concrete decisions.

If you want reviews to really work:

👉 don't increase the number of reviews
👉 just separate out what these meetings are for

Once a year - decisions.
Once a quarter - direction.
Day to day - feedback.

How to avoid overloading managers with the review process

One sentence you'll hear from managers in most companies is: "we don't have time for these performance reviews."

And very often it's true. It's just that the problem isn't the review process itself, but how it plays out in practice.

If there are no standards, everyone does it their own way, communication is unclear, and feedback shows up once every few months… then the performance review turns into a heavy, time-consuming process that takes a long time to prepare for.

I've seen teams where managers spent hours on a single review, because they had to "reconstruct" a year of the team's work from memory.

On the other hand, when you have a simple framework, clear rules, and daily feedback in place, everything looks much better.

The manager sits down for the conversation and, in truth, already knows the answers. Because they talked with that person earlier, saw their work, and responded along the way.

In that case the review doesn't take hours. It often wraps up in 45-60 minutes and stays concrete.

👉 It's not extra work
👉 It's a natural summary of what already happened

And that's exactly what we should be aiming for.

To wrap up

A well-designed performance review process isn't an extra chore, but a tool for making better business decisions. The key isn't the number of meetings, but their role and how well they fit with the team's everyday work.

If you separate feedback, progress monitoring, and decisions, the whole process becomes simpler, shorter, and far more effective.

To make it easier for you to put this into practice, I've prepared a ready-made annual review cycle template for you - broken down by stages, roles, and moments throughout the year.