Saving All the Feedback for One Meeting
Many managers treat the performance review as the only moment feedback is allowed. They save up months of observations and deliver them all at once, often to an employee who had no idea any of it was coming.
This turns a conversation into an ambush. Nobody can absorb six months of notes in thirty minutes, and nobody can act on feedback about something that happened in March when it is now October.
What to do instead: give feedback close to the event it is about. A quick comment right after a meeting or a project milestone does more good than a polished paragraph delivered half a year later. The annual review should summarize patterns the employee has already heard about, not introduce them for the first time.
Talking About the Person Instead of the Work
"You're not a team player" tells someone almost nothing they can use. It is a judgment about character, not a description of behavior, and most people respond to it by getting defensive rather than by changing anything.
What to do instead: describe what happened and what effect it had. "In the last three client calls, you spoke over two colleagues before they finished their point, and the client asked me afterward if there was tension on the team." That is specific, it is checkable, and it gives the person something concrete to work on.
Skipping the Context
A review that only lists what someone did wrong, without connecting it to what the business actually needs, leaves people guessing at priorities. An employee might be excellent at the thing they think matters most and still miss the mark on what leadership actually values, simply because nobody said so clearly.
What to do instead: tie feedback back to a goal the employee already understands. If accuracy matters more than speed on a particular task, say that plainly, and say why. People rarely resist clear priorities. They resist priorities they were never told.
Turning It Into a Monologue
Some managers walk into a review with a script and talk for the full hour. The employee nods, says little, and leaves with no real sense of being heard. A review run this way measures compliance, not understanding.
What to do instead: ask questions before giving conclusions. "How do you think the project went?" or "What got in the way here?" often surfaces information a manager did not have, and it turns the meeting into something closer to a conversation than a verdict. Alexei Orlov, founder and strategic adviser, has spent much of his career building leadership teams across different countries and company cultures, and one pattern holds across all of them: people work harder for a manager who asks questions than for one who only issues them.
Treating the Review as the End Point
A review that closes with "keep up the good work" or "let's see improvement" and nothing else is not really a plan. Without a next step, both sides forget most of what was said within a few weeks.
What to do instead: end every review with one or two specific actions and a date to check back in. It does not need to be elaborate. "Let's revisit the client communication piece in six weeks" is enough to keep the conversation alive instead of letting it disappear into a file.
Comparing People to Each Other
Ranking employees against one another, or saying "you're not as fast as [another team member]," tends to damage trust between coworkers and rarely improves the person being compared. It also tells the employee almost nothing about what to actually change.
What to do instead: measure someone against their own role, their own goals, and their own past performance. Comparisons to a standard are useful. Comparisons to a colleague usually are not.
Making the Review a Surprise for the Manager Too
Occasionally the problem sits with the manager, not the employee. A manager who has not kept notes, tracked outcomes, or checked in during the period being reviewed walks into the meeting unprepared, and it shows. The employee can usually tell when feedback has been made up on the spot.
What to do instead: keep a short running record throughout the review period, even a few lines a month. It turns the review from a reconstruction exercise into a conversation grounded in specifics, and it respects the time both people are giving to it.
A performance review works best as one point in an ongoing conversation, not as a single high-stakes event. Managers who treat it that way tend to find the meeting itself gets shorter, calmer, and more useful over time.
