How to Run a Year-End Review Your Team Won’t Dread

Think back to the worst year-end review you ever sat through. A small conference room, a form with 14 competencies, a manager reading from a screen and a rating of 3 out of 5 that seemed to have been decided weeks earlier.

You left with a raise number and no idea what to do differently in January.

Now it is your turn. The calendar says December, your team is waiting for their invites, and you would like at least one of them to walk out feeling better than you did.

Why do most year-end reviews go so badly?

Because they try to do three jobs in one meeting: judge the past year, set pay and plan growth. Each job pulls in a different direction, and the person in the chair can feel it.

The numbers back up the frustration. Gallup’s research on performance management found that only 2 in 10 employees strongly agree their performance is managed in a way that motivates them to do outstanding work. Just 21% strongly agree they have performance metrics within their control.

Some large employers have rebuilt the process entirely. Adobe says it dropped annual performance reviews and ratings in 2012 in favor of ongoing “Check-in” conversations, held quarterly. Deloitte described redesigning its own system in a widely read Harvard Business Review article by Marcus Buckingham and Ashley Goodall, because the old process no longer fit what the firm needed.

Most companies will still hold some kind of year-end conversation in 2026. The goal is to make it one people can use.

What should you do before the review meeting?

Good reviews are mostly won in the prep. Give yourself, and the employee, two weeks.

• Collect evidence from the whole year. Go back through project notes, wins, misses and messages from January on. Recent events crowd out earlier ones if you rely on memory.
• Ask the employee for a short self-review. Three questions are enough: What are you proudest of? What would you do differently? What do you want to learn next year?
• Talk to one or two peers. Ask what this person does that makes their work easier, and one thing they could do better.
• Decide what the meeting is not for. If pay is handled separately, say so in the invite. If it is not, plan for it explicitly.
• Write your top three messages. If they remember only three things, what should they be?

How should you structure a year-end review conversation?

A simple three-part agenda keeps the meeting from sliding into a list of grievances. Plan for about 45 minutes.

Part 1: Look back together (15 minutes)

Start with their self-review, not your form. Let them talk first about what went well and what did not.

Then add your view. Name two or three specific contributions and what they made possible. “Your vendor renegotiation in May freed up budget for the hire we made in August” lands better than “great job on vendors.”

When you get to misses, borrow a habit from software teams. Google’s site reliability engineers use blameless postmortems that focus on the contributing causes of a problem without indicting any person or team, and assume people did the right thing with the information they had. Applied to a review, that means asking what made the miss likely, not just who missed.

Part 2: Look forward (20 minutes)

This is the part most reviews rush, and it is where the value is.

Agree on two or three goals for the first half of next year. Write them together. Gallup found that employees who strongly agree their manager involves them in setting goals are 3.6 times more likely to be engaged than other employees, yet only 30% strongly agree that happens.

Then ask about growth. What skill do they want to build? What kind of work do they want more of? What would make next year better than this one?

Part 3: Decide and confirm (10 minutes)

Close with clear next steps: the goals you agreed on, one development commitment from you, and when you will check in next. Send a written summary the same day.

If pay is part of the meeting, cover it here, briefly and directly, after the forward-looking conversation is done.

Should pay be discussed in a year-end review?

Many companies tie the two together, but there is a strong case for separating them when you can.

Once a number is on the table, it tends to drown out everything else. People spend the rest of the meeting decoding it rather than listening to feedback.

Budgets also make the pay part harder this year. Gartner’s CFO budget benchmark, published Feb. 10, 2026, found that average pay increases slowed from 6.1% in 2024 to 5.4% in 2025, with 4.5% expected for 2026. Smaller raises make a strong development conversation even more important, because growth is part of what employees are weighing.

If you must combine them, be honest about the constraints. Explain how the number was set, what the range was and what would change it next year. Do not promise what you cannot deliver, and check your company’s pay and documentation policies with HR before the meeting.

What should you avoid saying in a performance review?

A few phrases do more damage than managers realize.

Avoid	Try instead
“You always…” or “You never…”	“In the Q3 launch, I noticed…”
“Everyone feels that…”	“Two people on the project told me…”
“You need to be more strategic.”	“Next quarter, I would like you to own the pricing analysis.”
“This is just how the ratings came out.”	“Here is how the rating was decided, and what would move it.”
“Any questions?” at minute 44	“What is the one thing you want to make sure we cover?” at minute 5

The pattern is the same in every row. Specific beats general, and their voice belongs early in the meeting, not as an afterthought.

How do you review someone who had a hard year?

Do not surprise them. If performance has been a real problem, they should already know from conversations earlier in the year. A year-end review is the wrong place for first news.

Separate the person from the result. Name the gap clearly, describe its impact and ask what got in the way. Sometimes the answer is skill. Often it is unclear expectations, a broken process or a workload problem the manager helped create.

Then agree on a short, concrete plan with dates. If the situation could lead to formal action, involve HR before the meeting and follow your company’s process. Employment decisions carry legal risk, so get professional guidance rather than improvising.

How should executives review other executives?

Senior reviews often get skipped or squeezed into a dinner. That is a mistake, because a vice president who gets no real feedback tends to pass the same silence down the line.

The same three-part agenda works, with a few adjustments. Spend more of the look-back on decisions rather than tasks: which calls turned out well, which ones you would make differently and what information was missing at the time.

Spend more of the look-forward on the team they lead. Ask who on their team is ready for more, who is struggling and what they need from you to build a stronger bench next year.

And ask for feedback on yourself. A senior leader who models taking criticism makes it far easier for everyone below them to do the same.

How do you run reviews for remote or hybrid teams?

The structure stays the same. A few details change.

• Use video, not just audio. Tone carries more weight in feedback than in most conversations.
• Share the written summary on screen at the end so you both see the same goals and next steps.
• Watch for proximity bias. People you see in person more often can seem more productive than they are, and remote employees can fade from view.
• Collect peer input deliberately from people in other locations, not just the ones nearby.

Our guide to leading hybrid teams with outcome-focused goals covers the norms that make distributed feedback work.

How do you make the review useful all year?

The best year-end review is mostly a summary of conversations that already happened. That is the lesson behind moves like Adobe’s: regular check-ins mean December holds no surprises.

Put a 20-minute check-in on the calendar for the end of each quarter. Use the same three questions each time: What is going well? What is in the way? What do you need from me? Then the next year-end review becomes a recap rather than a reckoning.

It also helps to treat the review as a decision you are making with the employee, not a verdict you hand down. Our recent column on optimizing for great decisions rather than revenue makes a related case: better choices come from better inputs and honest conversation.

What does a good year-end review feel like from the other chair?

Go back to that conference room, the 14 competencies and the rating decided in advance. This year, the same room can feel different.

The employee talks first. You name specific wins and look at misses without blame. You write next year’s goals together, explain the pay number honestly and commit to one thing you will do for them. They leave knowing exactly what to do in January.

That is the review you never got. It is the one your team will remember.

Frequently asked questions

How long should a year-end performance review be?

About 45 minutes to an hour works for most roles. That leaves time to look back, plan the next year and agree on next steps without rushing the forward-looking part.

Should employees write a self-evaluation?

Yes, a short one helps. Three questions are enough: what they are proudest of, what they would do differently and what they want to learn next. It gives the employee a voice and shows the manager what matters to them.

What is recency bias in performance reviews?

Recency bias is the tendency to weigh recent events more heavily than earlier ones. Reviewing notes and results from the whole year, not just the last few months, helps reduce it.

Are annual performance reviews going away?

Some companies, such as Adobe, have replaced annual reviews with regular check-ins. Many others still hold a year-end review but add quarterly conversations so the annual meeting holds no surprises.

How do you give negative feedback in a review?

Be specific, describe the impact and ask what got in the way before proposing a plan. Serious performance issues should never be raised for the first time at year end, and HR should be involved if formal action is possible.

Sources

• Gallup: Re-Engineering Performance Management
• Adobe: Check-in
• Harvard Business Review: Reinventing Performance Management
• Google SRE Book: Postmortem Culture: Learning from Failure
• Gartner: CFOs' budget plans prioritize growth functions, technology and AI in 2026