Almost every organisation appraises annually, and almost none can point to a behaviour that changed because of it. The reason is structural: feedback delivered months after the event, covering a whole year, attached to a pay decision, is feedback nobody can act on.
Why the annual review fails
Three problems compound each other. Recency, where the last two months dominate a twelve-month assessment. The pay conversation, which makes the employee argue rather than listen. And vagueness, because nobody remembers specifics from March.
You do not fix this by improving the form. You fix it by changing the frequency.
Short, frequent, specific
A monthly conversation of twenty minutes beats an annual one of two hours. It is close enough to the work that examples are fresh, low-stakes enough that people listen, and frequent enough that a small correction stays small.
Three questions carry most of it:
- What went well since we last spoke, specifically?
- What did not, and what got in the way?
- What is the one thing to focus on before we next meet?
That third question is where the value is. One thing, agreed, written down, reviewed next time.
Separate development from pay
The moment money enters the room, the conversation becomes a negotiation. The employee's job becomes to justify, not to reflect, and every admission of difficulty feels expensive.
Hold the pay conversation separately, on a different date. The development conversation can then be honest in both directions.
Be specific enough to be useful
"Improve your communication" is not feedback; it is a complaint. Useful feedback names the situation, the behaviour and the effect: "In Tuesday's meeting the figures were presented without the assumptions behind them, so the team spent twenty minutes questioning the numbers instead of deciding."
That version can be acted on. The vague version leaves the person guessing, and usually guessing wrong.
Ask before telling
Open with the person's own assessment. Most people know where they are struggling, and hearing it from them changes the conversation from judgement to problem-solving. It also occasionally reveals that the problem is not theirs at all — an unclear brief, a missing tool, a colleague not delivering.
Write it down, briefly
A few lines after each conversation: what was discussed, what was agreed, by when. It takes two minutes and it does three jobs. It gives the employee something to refer to, it means the next conversation starts from the last one, and it builds the record you need if performance does not improve.
When it is not improving
Informal conversation is the right first response, but it is not indefinite. When repeated, specific feedback has not produced change, move to a documented process: state the required standard, the gap, the support being offered, the review date, and the consequence if the standard is not met.
Two failures are common here. Moving to formal process too early, without giving honest feedback a chance. And leaving it too long, so the first formal step lands as a shock after two years of "satisfactory" appraisals — which is both unfair and very hard to defend later.
What managers need
Most managers avoid these conversations because they were never taught to have them and fear the reaction. The fix is not a better form. It is training, a simple structure to follow, and senior managers who visibly do it themselves.
An organisation where the leadership team holds monthly conversations gets them everywhere else. One where it does not will not get them from a policy.
