How to Write a Performance Review That Encourages Real Growth

Performance review season often arrives with the same uncomfortable question: How do I sum up months of someone’s work without sounding vague, harsh or unfair?

Gallup research, cited by the Financial Times, found that only 14% of employees strongly agreed that their performance reviews inspired them to improve. To me, the problem is not the review itself, but how it is written and delivered.

When people ask me how to write a performance review, my answer is simple: write it to create clarity, not merely to complete a process. A useful review should help an employee understand what went well, what needs attention and what they can do next.

What Does Writing a Performance Review Really Mean?

Writing a performance review means assessing an employee’s work over a defined period and recording that assessment in a fair, specific and useful way.

It usually covers results, strengths, behaviour, development areas and future goals. A good review also turns past performance into a practical conversation about future progress.

I see the written review as the starting point for that conversation, not the final verdict on a person. It should reflect what happened, explain why it mattered and show where the employee can go from here.

That becomes much easier when the writing follows a clear process.

How to Write an Effective Performance Review: A Simple Process

1. Revisit the employee’s role and goals

I begin with the expectations agreed at the start of the review period. What outcomes was the employee responsible for? Were those expectations clear and realistic?

This keeps the review tied to the role rather than to personal preference.

2. Gather evidence from the full review period

I look at goals, project outcomes, deadlines, customer feedback, peer input and notes from check-ins. Relying on memory alone can cause recent events to overshadow months of earlier work.

The evidence does not have to be entirely numerical, but it should be observable.

3. Identify the main performance themes

Before drafting, I group the evidence into achievements, strengths, challenges and development needs. This creates a balanced picture instead of a list of unrelated incidents.

4. Write with a situation–action–impact structure

For each important point, I describe the situation, the employee’s action and its impact.

Instead of writing, “Riya communicates well,” I might write: “During the product launch, Riya shared weekly updates with sales and support, which helped both teams resolve customer questions before release.”

The second version tells the employee exactly what effective communication looked like.

5. Turn improvement areas into clear next steps

“Needs to be more proactive” gives an employee very little direction. I would make it practical: “Over the next quarter, raise delivery risks during the weekly project meeting and propose at least one possible response.”

Useful feedback points towards an action the employee can repeat, change or learn.

6. End with agreed priorities

I finish with two or three goals, the manager’s support and a date to review progress. The process should help establish and monitor development objectives, not simply record a rating.

The Do’s of Writing Performance Reviews

• Be specific. Refer to actual work, decisions or behaviour rather than making broad claims.
• Cover the entire period. Use notes from regular check-ins so one recent success or mistake does not dominate the review.
• Balance recognition with development. Acknowledge meaningful contributions while being honest about what needs to improve.
• Discuss behaviour, not personality. Write “updates were often shared after the deadline,” rather than “you are careless.”
• Recognise context. If goals changed, resources were limited or another team caused delays, include that context instead of placing every outcome on one person.
• Make it a two-way conversation. Leave room for the employee’s view, including obstacles or achievements the manager may have missed.
• Keep the language clear. The employee should not need to decode corporate phrases to understand the message.

What Should You Avoid in a Performance Review?

First, avoid surprises. A serious concern should be raised when it happens, not stored until the annual review. Regular feedback makes the formal discussion fairer and more useful.

Avoid vague praise as well. “Great job this year” may sound positive, but it does not tell the employee what to continue doing.

I also avoid absolute words such as “always” and “never.” They are difficult to support and can make the conversation defensive.

Do not compare one employee with another. Compare performance with agreed expectations, goals and role requirements.

Finally, do not soften an important concern until its meaning disappears. Respectful feedback can still be direct. State the gap, give evidence, explain its effect and agree on the next step.

Examples of Well-Written Performance Review Comments

Example 1: Strong performance

“Arjun exceeded his quarterly retention target in three of the four quarters. He also created a renewal tracker that gave the sales team earlier visibility into at-risk accounts. His next opportunity is to document this approach so other account managers can use it.”

Example 2: Meeting expectations with room to grow

“Meera delivered her assigned campaigns on schedule and worked well with design and sales. Reporting quality improved during the second half of the year. In the next quarter, she should move beyond reporting activity and add a short explanation of what influenced results and what she recommends changing.”

Example 3: Performance needs improvement

“Three client reports were submitted after the agreed deadline this quarter, leaving the account team with limited review time. We have agreed that Kabir will confirm timelines at the start of each project, flag risks at least two working days in advance and review progress with his manager every Friday for the next eight weeks.”

Example 4: Leadership and collaboration

“Nisha supported two new team members through onboarding and regularly shared helpful project context. Both employees were able to manage their core tasks independently within six weeks. Her next goal is to use the same structured support when delegating work across the wider team.”

Each example works because it explains the evidence, the impact and the next step. That is the standard I use whenever I think about how to write a performance review that feels fair and useful.

A Good Review Should Make the Next Step Clear

A performance review should not leave an employee wondering what the manager really meant. It should recognise contribution, address gaps honestly and create a shared plan for growth.

The strongest reviews are also connected to the conversations that happen throughout the year. JOP helps organisations bring goals, check-ins, feedback and review cycles together, so managers can base evaluations on ongoing performance rather than scattered notes or memory.

If you want performance reviews to become more consistent, evidence-based and growth-focused, JOP can help you build a process that supports better conversations from one review cycle to the next.