Why annual reviews don't work, and what to do instead

Annual reviews fail because waiting twelve months to give feedback breaks almost everything that makes feedback useful. Recency bias takes over, so only the last few weeks get remembered. Feedback arrives too late to act on. And a full year of work gets compressed into one high stakes meeting instead of an ongoing conversation. The fix is not more reviews, it is a seasonal rhythm: set goals at the start of a season, track progress as it happens, and reflect at natural checkpoints along the way instead of only at the end.

Ask most people how they feel the week before their annual review, and you will hear some version of dread. Not because they had a bad year necessarily, but because a whole year of work is about to get compressed into one conversation, based mostly on whatever their manager happens to remember from the last few weeks.

What goes wrong when you wait a year

Recency bias takes over. Managers naturally remember what happened recently far better than what happened in February. A strong first half of the year can quietly disappear by review time, and a rough couple of weeks right before the review can dominate the whole conversation.

Feedback arrives too late to help. If something needs to change, hearing about it eleven months after it happened is not useful feedback anymore. It is closer to an accusation, delivered too late for the person to have done anything differently.

It turns into a single high stakes event. When all the feedback for a year lands in one meeting, that meeting carries enormous emotional weight. People brace for it. Some avoid preparing for it entirely because thinking about it is stressful. Neither reaction helps anyone grow.

It has almost nothing to do with daily work. Goals get set in January and forgotten by March. The review, when it finally happens, often feels disconnected from what someone actually spent their year doing.

A seasonal rhythm instead

The alternative is not "more reviews." It is a different shape entirely: work happens in seasons, usually a quarter or a year, and each season has a simple rhythm running through it instead of a single event at the end.

• Set goals at the start of the season, so everyone is clear on what matters before the work begins, not after.
• Track progress as it happens, a few minutes at a time, so nothing has to be reconstructed from memory later.
• Reflect at natural checkpoints partway through the season, not just at the very end, so there is still time to act on what comes up.
• Treat reflections as checkpoints, not closers. Goals stay open and editable after a reflection. Nothing gets locked in or judged as final until the season actually ends.

Checkpoints, not verdicts

The most important shift is not the calendar, it is the tone. A good reflection checkpoint is a two way conversation: the employee reflects honestly, the manager responds, and both sides get a real say before anything is considered settled. That is very different from a manager handing down a verdict that the employee has to accept.

When people trust that a checkpoint is a conversation rather than a judgment, they tend to write more honestly, raise concerns earlier, and actually use the feedback instead of just enduring it.

What this looks like in practice

This is the model Grove is built around. A season replaces the once a year cycle of waiting. Reflection checkpoints replace the single high stakes review. And every review stays private and two way until both people are ready to close it together, not the moment one person hits submit.

The goal is not to add more process. It is to spread the same conversation across the year, at moments when it can actually help, instead of saving it all up for one stressful afternoon in December.

Frequently asked questions

How often should reflection checkpoints happen?

Most teams do well with two or three checkpoints across a season. Frequent enough that there is something real to reflect on, not so frequent that it starts to feel like surveillance.

Do goals need to be finalized before a checkpoint?

No. Goals should stay open and editable after a reflection. A checkpoint is a pause to look back, not a moment where anything gets locked in as final.

What replaces the annual review rating?

Nothing needs to replace it directly. A seasonal rhythm shifts the emphasis from a single score to an ongoing, two way conversation, so the review stops being the only moment feedback happens.