Most performance reviews end with a document nobody opens again.
The manager ticks boxes. The employee nods. Someone writes “leadership development” in the goal box. Then both go back to their desks and everything continues exactly as before.
It’s not the conversation’s fault. It’s the structure’s.
What goes wrong with performance reviews
The problem is that most performance reviews are backward-looking. You talk about what happened the past year. You rehash a few things that did not work. You write down some agreement for the coming year.
Then you forget it.
Almost every manager I talk to recognizes this. They block an hour, do the review, fill in the template, and never follow up on anything that was said. Not because they are careless, but because there is no natural rhythm for follow-up. The review exists as an isolated event, not as part of an ongoing collaboration.
That gives you a conversation that is better than nothing, but not by much.
What separates the good ones from the empty ones
Managers who succeed with performance reviews do three things differently.
They plan for follow-up when they book the conversation. Almost every manager books the review. Few book a shorter check-in three months later. It does not matter how good the agreement is if there is no opportunity to actually look at it. A 20-minute check-in in the calendar right when the review is done, not when someone remembers it at year-end.
They make agreements concrete enough to be something. “Leadership development” is not an agreement. It is a thought. An agreement is: “We sign you up for the PMI course starting in March, and I set up a project where you lead the delivery for the Stockholm client.” The difference is that one is verifiable. The other is something you nod at.
They separate salary conversations from development conversations. When salary is discussed in the same meeting as goal-setting, the employee talks strategically, not honestly. That is human. But it means you are less likely to learn what they actually need to grow. Keep them separate, and most agree you should, and you get two conversations where both can be honest.
The follow-up problem is a system problem
A common reaction is that you make the agreement in the moment. True. But what happens next is a structure problem, not an intention problem.
If the information about what you talked about, what you agreed on, and what happened afterward lives in a PDF in a folder tree on an intranet nobody finds, follow-up depends on someone remembering to look for it. That is a bad system. Not because people are careless, but because memory is not a system.
This is also why the permissions question is underestimated. Who should actually see the review’s content? Just the manager and the employee? HR too? The manager’s manager? When you need manual handling per review, it slips through in the rush. And when it slips through, sensitive information ends up accessible to the wrong people, or you lock it down so tight that nobody can access it at all.
The right approach is that the system knows who the manager is and who the employee is, and assigns the right access without anyone needing to remember to do it.
Are annual performance reviews worth the effort?
Yes. But not for their own sake.
Performance reviews are one of the few occasions where a manager and an employee actually sit down, without a customer meeting agenda, and talk about how things are going. About what works. About where the employee wants to be in three years. About what the company needs that this person could contribute.
That occasion is worth taking seriously. Not because it says so in a contract or because HR sends reminders, but because it is one of the few tools for actually leading someone, not just administering them.
But if the review ends with a document that never opens again, then it was an hour that disappeared.
Start here: what happened with the agreements you made last year? If the answer is “don’t know,” you found the problem. The structure is broken, not the intention.
In AmpliFlow, permissions for performance reviews are handled based on how the organization actually looks. HR gets edit rights at the module level. Managers and employees are added as users and automatically see the right reviews based on the reporting hierarchy, without manual handling per review. The templates can be built freely with text fields, task lists, dropdowns, date fields, and more. Read our guide for staff appraisals in AmpliFlow if you want to see how it works.
