How to Run a Performance Review That Actually Helps

Almost everyone has sat through a bad performance review: vague, one-sided, dreaded by both people in the room, and forgotten a week later. That is a shame, because a good review is one of the most useful management tools there is. The difference is not the form. It is the approach.

Here is how to run a review that is fair, specific, and actually moves performance. The free template above gives you the structure.

What makes reviews fail

Most bad reviews share a few traits. They are based on recent impressions rather than the whole period, so they feel arbitrary. They are vague, so the employee cannot act on them. They are one-sided, delivered as a verdict rather than discussed. And they are disconnected from any clear goals, so nothing concrete comes out of them. Fixing those four things is most of the battle.

Before the review: prepare with specifics

The quality of a review is set before the conversation starts. Gather specific examples from across the whole review period, not just the last few weeks, because recency bias is the most common way reviews go wrong. Base each competency rating on something concrete the person actually did. The goal is that every point you make can be backed with an example, because specifics are what make feedback credible and actionable.

What to cover

The template walks through a structure that works for small teams:

Goals from last period

Start by reviewing the goals you set last time and how each turned out. This anchors the review in agreed expectations rather than shifting impressions.

Core competencies

Rate the things that matter for the role: quality of work, reliability and ownership, communication, collaboration, and role-specific skills. Use a simple scale, and attach a specific example to any rating, especially the high and low ones.

Strengths and development areas

Be honest about both. Name what the person does genuinely well, with examples, because recognition that is specific actually lands. Then name where there is room to grow, framed as development rather than failure, again with specifics. A review that is all praise is useless, and one that is all criticism is demoralizing; the honest middle is what helps.

Goals for next period

End by setting two to four specific, measurable goals with timelines. This is what turns the review from a backward-looking assessment into a forward-looking plan, and it gives you the anchor for the next review.

The conversation itself

Run it as a two-way discussion. The employee should talk at least as much as you do. Ask for their view on how the period went, where they want to grow, and what they need from you. Listen to the disagreements, because sometimes a low rating reflects something you did not see. End with alignment on the goals ahead and space for their written comments, then both sign off.

How often to review

An annual review alone is too infrequent to be useful. The stronger pattern is regular lighter check-ins (monthly or quarterly one-on-ones) plus a more formal review once or twice a year. Frequent feedback means nothing in the formal review is a surprise, which is exactly how it should be.

A note on pay

It often helps to keep the development conversation somewhat separate from the compensation conversation. When the whole review is really about the raise, the developmental value evaporates. You can hold them close together but distinct, so the feedback gets heard on its own terms.

The bottom line

A good performance review is specific, fair, two-way, and forward-looking, and it is one of the best tools a manager has. The template above gives you the structure; the specifics and the honest conversation are what make it work. If you want help building a review process or coaching your managers to run them well, that is part of what we do.