If an employee first hears about a serious performance concern during an annual review, the review is not evidence of a strong accountability system. It is evidence that the conversation arrived late.
Annual reviews are often treated as the moment when leaders finally become candid. Notes are gathered, examples are organized, ratings are defended, and months of frustration are compressed into one meeting. The employee experiences the history all at once, after many opportunities to adjust have already passed.
The contrarian truth is that delayed feedback often protects the leader more than the employee. The leader avoids discomfort in the moment and transfers the accumulated cost to the person later.
Feedback should change the future.
Useful feedback is not a verdict on someone's character. It is timely information that helps a person make a better next choice. The closer the conversation is to the behavior, the easier it is to remember the context, test assumptions, and agree on what should change.
This does not require constant correction. Leaders who comment on everything create dependence and anxiety. The discipline is to address patterns and consequential moments early enough that the employee still has room to act.
The same week standard.
Use a simple operating rule: when a behavior is important enough to influence a future rating, promotion, assignment, or employment decision, discuss it within the same week whenever practical. Safety, ethics, or serious misconduct may require immediate action. Ordinary coaching should not be stored for months.
A short conversation can follow five moves. First, name the observable moment without exaggeration. Second, explain the effect on the work, customer, or team. Third, ask for the employee's view before reaching a conclusion. Fourth, agree on the next behavior and the support required. Fifth, set a specific time to revisit the change.
For example
"In yesterday's project review, the risk was raised after the decision rather than during the discussion. That left the team without time to test it. What made it difficult to raise earlier? Next week, I'd like you to flag risks as soon as you see them, even if the analysis is incomplete. I'll make space on Thursday to review what happened."
Separate coaching from documentation.
Documentation matters, but it should record a conversation rather than replace one. After meaningful coaching, capture the date, the observable behavior, the agreed action, the support offered, and the follow-up point. Avoid labels such as poor attitude or lacks commitment. They are conclusions, not usable evidence.
A reliable review should summarize a year of known conversations. It should not reveal a hidden case the manager has been building.
Kind leadership does not remove discomfort. It refuses to make discomfort more expensive by postponing it.
The ARC leadership practice.
Authentic self-leadership notices when our desire to be liked is delaying clarity. Reflection tests whether the feedback is specific, fair, and connected to a real standard. Courage delivers the message while improvement is still possible.
Implementation Checklist
- Identify any feedback currently being stored for a future review.
- Schedule the conversation within the same week.
- Use the five moves: moment, effect, perspective, next behavior, follow-up.
- Document the agreement using observable language.
- Review progress on the date you promised.
A review should recognize progress and summarize known gaps, not reveal concerns the employee was never given a fair chance to address.
Questions for Reflection
- What concern could surprise someone at review time?
- Am I delaying the conversation because more evidence is needed or because I am uncomfortable?
- What support will make the expected change achievable?