Exceeds expectations
- Closes more support tickets a day than the team average while keeping reopen rates low, so volume does not cost quality.
- Clears the full invoicing backlog before month end, so finance closes the books without chasing pending bills.
- Processes joining paperwork for a large intake in two days, so new hires start on the promised date.
- Handles the counter rush single-handed during a colleague's leave without letting the queue build past a few minutes.
- Meets the weighted output goal every cycle and picks up spillover work once own tasks are done.
- Keeps the dispatch line moving at a steady rate through the shift, rather than a fast start and a slow finish.
- Reworks a slow manual step into a quicker routine, lifting the whole team's daily throughput.
- Finishes assigned data entry ahead of schedule and uses the spare time to clear the pending queue.
Meets expectations
- Completes the daily target on most days and flags early when a backlog is building.
- Keeps a steady pace through the shift rather than rushing the last hour to hit the number.
- Handles the normal case load without needing tasks reassigned to colleagues.
- Clears routine work on time and asks for more once the queue is empty.
- Balances speed with accuracy, so faster output does not create rework for the team.
- Meets the agreed weighted goals for the cycle within the planned effort.
- Recovers a slow morning by re-sequencing the afternoon rather than letting the day's total slip.
- Keeps personal trackers current, so the manager can see real output without asking.
Needs improvement
- Output dips in the second half of the shift, so the daily target is missed more often than met.
- Starts several tasks at once and finishes few, so throughput looks busy but stays low.
- Waits for work to be assigned rather than pulling the next item from the queue.
- Lets a backlog build quietly and raises it only when it is too large to clear in a day.
- Trades accuracy for speed under pressure, so gains in volume are lost to rework.
- Needs tasks reassigned during normal weeks, not just peak ones, to meet the team's numbers.
- Keeps trackers up to date late, so the real output is hard to gauge mid-cycle.
Self-review phrases
- I pull the next ticket from the queue now instead of waiting for it to be assigned.
- I kept my output steady across the shift this cycle rather than rushing the final hour.
- I want to hold accuracy under pressure so my faster work does not create rework.
- I cleared the invoicing backlog before month end so finance could close on time.
Tips for writing this feedback
- Measure productivity against the goal set for the role, not hours logged or how busy the person appears through the day.
- Rate productivity and quality separately, so high volume with heavy rework is not mistaken for strong output.
- Check whether output holds through the shift or fades late, and whether peak weeks needed extra hands.
- Compare against the person's own past cycles and the team, not an ideal, so the target stays fair.
- Credit steady throughput and backlog cleared, not just a fast burst before the deadline that leaves errors behind.
Track goals and review cycles for every employee in ZeniaHR.
See it on your own data
A 30-minute demo on a video call. We set up your departments, shifts and leave rules and show attendance, leave and payroll running for your team. Free for your first 50 employees.
Book a free demoSee pricingFrequently asked questions
How do you measure productivity in a performance review?
Measure productivity against the output goal set for the role, using real numbers such as tickets closed, invoices raised or units dispatched. Compare against the person's own past cycles and the team rather than an ideal, and look at whether the pace held through the shift. Rate it apart from quality so volume alone does not carry the score.
Is working long hours the same as being productive?
No. Long hours show effort, not output. A person can stay late and still miss the target if time goes on low-value work or constant task switching. Judge productivity by what was finished against the goal, and treat many hours with little to show as a planning problem to solve, not a strength to reward.
How do I review productivity without hurting quality?
Set a goal that names both, then rate them on separate lines. Recognise volume only when rework stays low, and flag fast output that comes back for correction. When someone pushes numbers by cutting checks, address it as a quality gap, so the team does not learn that speed alone earns a good review.