One of the things I hear most often from employees, and more quietly from managers, is that the annual review ended up being the first time a real concern was named. An employee walks in expecting a routine conversation and walks out learning that something about their work has been a problem for months. The manager, meanwhile, often feels they were patient and fair by saving it for the formal conversation. Both people leave frustrated, and the trust between them takes a hit that is hard to repair.
What I have found is that this rarely comes from a manager who does not care. It usually comes from a system that treats feedback as an event instead of a habit, and from leaders who were never shown what regular, low-stakes feedback actually sounds like.
Why Feedback Gets Saved Up
There are a few reasons feedback tends to pile up until review season. The first is discomfort. Most people do not enjoy telling someone their work is missing the mark, so they wait for a moment that feels official enough to justify the conversation. The second is time. When managers are carrying their own workload alongside their team’s, a quick conversation about a small concern feels like something that can wait until next week, and next week becomes next quarter.
The third reason is structural. If the only formal place for feedback in an organization is the annual evaluation, then that is where feedback goes. People follow the system they are given, even when the system works against them.
What the Surprise Actually Costs
I want to be careful here, because the problem is not the annual review itself. A yearly conversation about growth, goals, and direction can be valuable. The problem is when it carries information that should have been shared months earlier.
When that happens, the employee loses the chance to adjust while it still mattered. The manager loses credibility, because the employee is left wondering what else has not been said. And the organization loses performance it could have had, because a correctable issue was allowed to run for most of a year. Over time, people also learn to brace for evaluations instead of learning from them, which makes every future feedback conversation harder.
Building a Rhythm Instead of an Event
Closing the feedback gap does not require a new software platform or a complicated process. It requires a rhythm that makes feedback normal, so that nothing in a formal review comes as news. A few practices help:
- Make feedback small and frequent. A two-minute conversation about one specific thing, close to when it happened, is easier to give and easier to hear than a list of concerns delivered all at once.
- Separate feedback from judgment. Describe what you observed and the effect it had, rather than offering a verdict about the person. “The report came in after the client call, so we went in without the numbers” is something someone can act on.
- Ask before you tell. Starting with “How do you think that went?” often surfaces what the person already knows, and turns the conversation into problem-solving rather than correction.
- Make it a two-way conversation. Leaders who ask their teams for feedback, and visibly act on it, make it much easier for feedback to travel in both directions.
- Use the annual review to summarize, not reveal. If the formal evaluation is simply a record of conversations that have already happened, it becomes a planning tool instead of an ambush.
When Feedback Still Isn’t Happening
Sometimes an organization does all of this on paper and feedback still does not happen. Managers say they are too busy, employees say they never hear anything until it is too late, and the cycle repeats. That is usually a sign the problem is not knowledge. Most managers already know they should be giving more feedback. Something is getting in the way of doing it: unclear expectations about whose job it is, workloads that leave no room for conversation, a culture where honest input has been punished before, or leaders who were never given feedback well themselves and are repeating what they learned.
That is where The Interrupt Framework™ starts: understanding what is actually interrupting the behavior before deciding how to fix it. Another training on how to give feedback will not help much if the real barrier is time, trust, or a pattern in how the team handles hard conversations.
Feedback works best when it is ordinary, timely, and expected. If your team only hears where they stand once a year, and you would like to talk through what is getting in the way, let’s talk.
Leave a Reply