Skip to the main content.
Talk to an expert
Talk to an expert
Featured Offer
Ambitious 50 →
6 months of Hire and Engage free for businesses under 50 people.

Hey Compono!

A coach that actually gets you.

Get 10 minutes free, then $15 a month. Cancel anytime.

Get Started ≫
Free tools for HR leaders

Productivity
performance review phrases

24 phrases across four rating bands, for managers, coaching conversations and self-evaluations. Filter, copy, print. Free, no sign-up.

Start with the rating band that matches the person, then pick the voice you are writing in. Copy a phrase, then change the specifics so it names the real project, the real quarter, the real thing that happened. A comment that could describe anyone is the thing you were trying to avoid.

How these were written, and the five steps to a review that holds up ↓
Rating:
Voice:
24 showing
Exceeds expectations

Output is high and the quality has not moved to pay for it.

Manager to employee

Removed a step from [process] that was costing the team a day a week.

Manager to employee

Knows what to stop doing, which is the harder half of being productive.

Manager to employee

Worth having them look at the team's process rather than only their own. The gains there are larger.

Coaching

Ready to own throughput for the team, not only their own.

Coaching

I cut [step] from our process after timing it properly, which gave the team back about a day a week.

Self-evaluation
Meets expectations

Delivers a full workload consistently without quality slipping.

Manager to employee

Uses the tools available rather than working around them by hand.

Manager to employee

Focuses on the work that matters rather than the work that is easiest to start.

Manager to employee

Productive at the individual level. The next step is spotting the process that is slowing several people down.

Coaching

Worth timing the thing you do most often. It is almost always slower than it feels.

Coaching

I automated the reporting I was doing by hand each week, which was about three hours I had stopped noticing.

Self-evaluation
Needs development

Output is lower than the role requires, and the gap is not explained by the work assigned.

Manager to employee

Continues with manual approaches where a tool is available and known.

Manager to employee

Effort concentrates on low-value work that is easier to finish.

Manager to employee

Rank your week by what it changes, not by what you can finish. Those two lists are rarely the same.

Coaching

Pick the task you repeat most and time it honestly. Then decide whether it should exist at all.

Coaching

I spend time on the work I can finish rather than the work that matters, because finishing feels better.

Self-evaluation

I still do several things by hand that the tools would do.

Self-evaluation
Unsatisfactory

Output has been materially below the role's requirement across the year, after being raised in [month].

Manager to employee

Work assigned has not been completed within reasonable timeframes without an identified cause.

Manager to employee

We need to agree what a normal week's output looks like, in writing, and review it weekly. Six-week assessment.

Coaching

Before we go further, I want to rule out whether the tools, the process or the workload are the constraint rather than you.

Coaching

My output has not been where it needs to be. I want an agreed definition of a normal week rather than guessing.

Self-evaluation
No phrases match those two filters together. Clear one of them.
How do you write about productivity in a performance review?

Rate what was produced against the standard it was produced to. High output at falling quality is not productivity, it is borrowing.

How these were written

Written, not calculated. Each phrase names a situation, an observable behaviour and its effect on the work or the people around it. Bands run from exceeds expectations to unsatisfactory across three voices: a manager writing about somebody, a manager coaching, and a person writing their own self-evaluation.

Assumptions
  • Phrases are starting points. Drop in the real situation or the comment reads as filler.
  • The four bands assume a four-point scale. On a three or five-point cycle the band is a sorting device, not a score.
  • Written for Australian workplaces and Australian English.
  • Check the constraint before rating the person. Workload, authority, tooling and what happened to the last person who tried shape most of what gets written up as an individual failing.
  • Unsatisfactory-band comments assume a dated record already exists and the issue has been raised before.
Sources

What to do about it

Good phrasing rescues a review that was already done properly. It cannot rescue one where nobody wrote anything down until the week it was due.

1

Start from your notes, not from this list

Open what you recorded during the year, pick what really happened, then find the wording. The other order produces a fluent review that says nothing.

2

Name the situation in every comment

The real project, the real quarter, the real result. Only one person could have earned it.

3

Match the band to your evidence, not the conversation you want

A generous rating on somebody you privately consider a problem is how next year's difficult conversation ends up looking like it came from nowhere.

4

Pair every development comment with a support step

Training, a pilot, a pairing, a cadence. Criticism without a path forward produces defensiveness and reads badly to anyone reviewing the file later.

5
Where a tool helps

Read your reviews as a set

If the same competency is the gap across a function, that is a capability gap in how the team was built rather than a dozen development plans.

Busy is not the
same as productive.

Compono Develop maps role requirements against real capability and load, which is what tells you whether the constraint is the person, the process or the workload.

Step 5 asks what your reviews say together. That is very hard to answer from a folder of review documents and straightforward to answer from capability data.

See how it works
Compono Develop
4.7/5
rating across millions of learners

Common questions

What are examples of productivity feedback?

Removing a step that was costing the team time, using the tools rather than working around them, choosing work by what it changes rather than what is easiest to finish.

How do you address low productivity?

Rule out the tools, the process and the workload first. If those are the constraint, no amount of performance management will move it.

Can I use these phrases word for word?

Yes, with the real work named.

These phrases are starting points, not finished comments. Change the specifics so each one is true of the actual person and the actual situation, because a comment that could describe anyone is the thing you were trying to avoid. Review comments can later be read as evidence in an employment matter, so anything you take from the unsatisfactory band should match a dated record you already hold. Last reviewed July 2026.

Next step

HR Glossary

Competency framework

The bands above are competency ratings. This is what a competency framework is, and how the levels are meant to work.

Read the definition →Related tool

Revenue per employee calculator

Reviews name the gap one person at a time. This one sizes it across the team.

Run it next →Buying

Requirements builder

Score the platforms you are looking at against the two risks, must-haves first.

Build the scorecard →Talk to us

Bring us your review cycle

A conversation about what your reviews are telling you as a set, not a demo script.

Talk to us →