illustration contrasting a generic performance review comment with a specific detailed one

37 performance review examples and phrases by competency

Performance Reviews Dmytro Shtapauk · Published August 5, 2026 · Updated October 22, 2026 · 19 min read
Share

A performance review comment that helps names one specific thing someone did and the effect it had. A comment that doesn’t is a label anyone on the team could wear: “great communicator,” “needs to be more proactive,” “solid team player.” Swap in a different name and nobody would notice. That gap, between a label and a real example, is what separates a performance review that changes something from one that gets filed and forgotten.

Search “performance review examples” and you’ll find lists of 100 or more phrases, sorted by competency and split into positive and constructive. They’re generic by construction, built to apply to anyone, which means they help no one in particular. This piece covers eight competencies, including quality of work, productivity and customer focus, plus final comments: the weak version, the specific version, and a line on why the difference matters.

Key Takeaways

  • A performance review comment that helps names a specific moment and its effect. A comment that doesn’t is a label, “great communicator,” “needs initiative,” that could apply to anyone on the team.
  • Quality of work and productivity are two different competencies. Judge accuracy and rework in one comment and output in another, or the slow-but-right person loses twice.
  • The move that makes a growth area receivable is naming the behaviour and its consequence, then pointing forward. Character labels make people defensive.
  • A final comment needs three things: what mattered most this period, the effect it had, and the one focus for next period.
  • Don’t copy these lines. Copy the pattern (moment, effect, one change) and you can write a comment for any situation a list doesn’t cover.

What makes a performance review comment actually useful

There’s a simple test: could this comment apply to more than one person on your team? If yes, it’s a label. “Reliable” could describe half the office. “Consistently hits deadlines on the Morrison account, even when scope changed twice mid-project” could only describe one person, because it’s built from something that actually happened.

Take the most common line in any review: “good communicator.” It commits to nothing. The specific version, “flags a blocked task the same day it happens,” names an actual behaviour and lets the reader picture it. The same failure shows up in multi-rater rounds too; why 360 feedback is always vague covers it there. Every example below follows one shape: a specific action, its effect, and for growth areas, the one change that would help.

Performance review examples for communication

As a strength. Weak: “Communicates well.” Strong: “Sends a short written recap after every client call, so nothing said on the call gets lost or misremembered a week later.” Why it works: it names a repeatable habit and the exact problem it prevents, which tells the person precisely what to keep doing under pressure.

As a growth area. Weak: “Needs to improve communication.” Strong: “Status updates tend to arrive once a deadline has already slipped, so the team finds out the hard way.” Why it works: it describes a pattern and its cost without touching the person’s character, which makes it easy to act on and hard to argue with.

Performance review examples for teamwork and collaboration

As a strength. Weak: “Great team player.” Strong: “When a teammate falls behind before a release, picks up part of the load without being asked and without keeping score.” Why it works: it’s a scene instead of a trait, and it tells the person exactly what behaviour earned the praise.

As a growth area. Weak: “Could collaborate more.” Strong: “Tends to solve the hard part of a problem alone and hand over the finished answer, so the rest of the team doesn’t see the reasoning until it’s too late to catch issues early.” Why it works: it names the specific habit and its downstream effect, rather than rendering a verdict on how collaborative the person is.

Performance review examples for ownership and initiative

As a strength. Weak: “Takes ownership of their work.” Strong: “When the deploy broke on a Friday, stayed to trace the cause, wrote up what happened, and updated the checklist so it can’t recur. Nobody asked for the last part.” Why it works: it’s a complete scene with a beginning and an end, and the unprompted detail (the checklist) is what earned the strength callout.

As a growth area. Weak: “Needs to take more ownership.” Strong: “Execution is strong once a task is defined. The next step is spotting the task before it’s assigned, the way the documentation gap last month sat unaddressed until someone else flagged it.” Why it works: it separates what’s already working from the one specific thing to grow, anchored to a real moment instead of a vague instruction.

Performance review examples for leadership

As a strength. Weak: “Strong leader.” Strong: “In the last planning meeting, named the two things the team is explicitly not doing this quarter, which made it obvious what to say no to when new requests came in.” Why it works: it turns “leadership” into a specific act with a visible effect on how the team makes decisions.

As a growth area. Weak: “Could be more consistent.” Strong: “The stated priority shifted from growth to retention in March, but the change was never named out loud, so part of the team kept optimizing for the old goal for weeks.” Why it works: it shows the cost of the inconsistency without questioning the person’s judgment, which keeps the comment developmental.

Quality of work performance review phrases

Quality of work is how good the output is: how accurate, how thorough, and how often someone else has to fix it. Generic phrases do the most damage here, because “pays attention to detail” never says which details.

As a strength. Weak: “Produces high-quality work.” Strong: “Reviews their own pull requests against the team’s edge-case list before asking for review, so reviewers spend their time on design questions instead of typos.” Why it works: it names the habit behind the quality and the cost it saves other people, which is the part the person can keep doing on purpose.

More strengths:

  • “The board report they prepared in June went out without a single correction, and finance reused that reconciliation sheet for the next two quarters.” The reuse is the evidence; it shows the quality held up beyond one deadline.
  • “Checks a colleague’s numbers before they go to a client, and caught the currency error in the Meridian proposal two days before it was sent.” A specific catch with a specific consequence avoided beats any adjective about thoroughness.

As a growth area. Weak: “Needs to improve attention to detail.” Strong: “The same two fields in the monthly report have needed correcting three months running. A two-minute check against last month’s figures before sending would catch them.” Why it works: it locates the problem exactly and makes the fix small, which turns a vague criticism into a habit the person can start next month.

More growth areas:

  • “Quality drops in the last two days before a deadline: the March and May releases both shipped with bugs the earlier sprints would have caught. Flagging a squeezed timeline earlier would protect the quality you already show the rest of the time.” It credits the normal standard and isolates the condition that breaks it.
  • “Spent four days polishing an internal draft that the team needed for a 30-minute discussion. Matching the polish to the use would free time for the client work that needs it.” This is a quality problem that looks like a strength, and naming it that way keeps the comment fair.

Productivity and quantity of work examples

Productivity, or quantity of work, is how much gets finished. Keep it in a separate comment from quality. A review that judges one by the other is unfair to the person who is slow and right, and lets the person who is fast and sloppy off the hook. “Works hard” describes effort, and only output belongs in a productivity comment.

As a strength. Weak: “Very productive.” Strong: “Closed about 40 support tickets a week through Q3 while keeping the reopen rate under 5%, the highest volume on the team without a quality cost.” Why it works: it uses a number the team already tracks and pairs it with a quality check, so the praise can’t be read as “fast but careless.”

More strengths:

  • “Finishes what they start: eleven of twelve sprint commitments delivered this half, and the twelfth was descoped by agreement.” Finishing is the part of productivity that lists of phrases skip.
  • “Unblocked three teammates in October by answering the API questions they were stuck on within the hour. Their own ticket count dipped; the team’s went up.” Some of the most productive work shows up in other people’s output.

As a growth area. Weak: “Needs to increase output.” Strong: “Has six tasks in progress and two finished this sprint. Finishing one before starting the next would move more work to done and make it easier for others to plan around.” Why it works: it describes the pattern that’s limiting output, which the person can change, instead of asking them to simply do more.

More growth areas:

  • “Is busy all week, but the proposal that was due in September is still in draft. Agreeing on two must-finish items each Monday would make the output match the effort.” It separates being busy from getting things done without calling the person lazy.
  • “Ships quickly, and roughly a third of tickets come back from QA. Slowing down by an hour per ticket would likely save more than an hour downstream.” Speed that creates rework is a productivity problem for the whole team.

Customer focus performance review examples

Customer focus is how well someone understands what the customer needs and acts on it. At a company of 50 people, most roles have customers even if they never talk to a buyer: the sales team is the engineer’s customer, and the managers are the HR lead’s. These examples work for either.

As a strength. Weak: “Customer-oriented.” Strong: “Calls clients a week after an issue is resolved to check it stayed fixed. Two of those calls turned into renewal conversations this year.” Why it works: it names a behaviour nobody required and connects it to an outcome the business cares about.

More strengths:

  • “Turns a vague customer complaint into a fix request engineering can act on: steps to reproduce, the account affected and what the customer expected.” Translating between customer and team is customer focus that most phrase lists never mention.
  • “Told a client clearly that the custom report they asked for wouldn’t happen this quarter, and offered the export that covered 80% of the need. The client stayed and used it.” Saying no well is part of serving a customer.

As a growth area. Weak: “Needs to focus more on the customer.” Strong: “Answers the question the client asked and closes the ticket, even when the question shows a bigger problem underneath. In the Halden account, three tickets in a month were the same setup issue.” Why it works: it points at a specific gap between the stated request and the real need, with a real account as evidence.

More growth areas:

  • “Promised the client a two-week turnaround the team had never hit. Checking with delivery before committing would protect both the client and the team.” It addresses the behaviour without suggesting the person doesn’t care.
  • “Internal requests from the sales team wait longer than client requests, without anyone being told. If they’re lower priority, saying so would let sales plan around it.” It treats internal customers as customers and asks for transparency rather than more speed.

Job knowledge performance review phrases

Job knowledge is what someone knows about their role, their tools and their field, and how they use it. The specific version usually shows what the knowledge made possible for someone else.

As a strength. Weak: “Has excellent job knowledge.” Strong: “Is the person the team asks about the payroll integration, and wrote the two-page guide that cut new-hire setup questions to almost none.” Why it works: knowledge kept in one head is a risk; knowledge written down for others is the strength worth naming.

More strengths:

  • “Knew the new EU invoicing rule before it applied to us and updated the templates a month early.” Staying current only counts when it changes what the team does.

As a growth area. Weak: “Should improve technical knowledge.” Strong: “The reporting dashboards were rebuilt in the new tool in April, and most of their reports still come from the old exports. A half-day with the analytics team would close the gap.” Why it works: it names the specific knowledge gap, its cost, and a concrete way to close it.

More growth areas:

  • “Knows the product deeply but tends to answer from memory, and two answers this quarter were about features that had changed. Checking the release notes before replying would keep the answers as good as the knowledge behind them.” It respects the expertise while naming where it goes stale.

Final comments and overall performance summary examples

The final comment is where most of this specificity quietly dies. Someone reads a dozen comments, tries to be helpful, and condenses them into themes: “communication came up a few times,” “collaboration is a strength.” The reviewee reads the theme, nods, and changes nothing, because there’s nothing left in it to act on.

A weak performance review summary: “Communication was mentioned as an area to work on.” A useful summary: “Three separate people independently described the same pattern: updates arrive once a deadline has already slipped. That’s specific enough to fix.”

The rule is simple: no theme without the example that earned it. A useful final comment has three parts:

  1. What mattered most this period.
  2. The effect it had.
  3. The one focus for the next period.

The same rule applies to a 360 report, where the comments belong next to the scores they explain.

Final comment for a strong year. “The biggest contribution this year was rebuilding the onboarding checklist: new hires now ship their first change in week one instead of week three. The focus for next year is passing that knowledge on, so the process doesn’t depend on one person.”

Final comment for a mixed year. “Client work was excellent, and the Meridian renewal happened largely because of the weekly check-ins. Internal deadlines slipped four times, though, mostly on documentation. For the next six months, the one focus is agreeing realistic dates up front and flagging early when they move.”

Final comment for a year with a real performance concern. “The quality of the analysis remains strong. Three of the five reports this half arrived after the agreed date, and in two cases the team had to make decisions without them. Between now and the March check-in, the expectation is that reports arrive on the agreed date, or that a delay is flagged at least two days ahead. We’ll review progress together every two weeks.”

That last one stays kind by being exact about the facts, the effect, the expectation and the support that comes with it.

Employee final comments on their own appraisal. Many performance appraisal forms give the employee the last word. Use it to add context or agree on next steps, with the same specificity.

  • Agreeing and committing: “I agree with the focus on estimating. I’ll share my estimate with the team lead before each sprint starts, so we catch overruns while there’s still time to change scope.”
  • Respectfully disagreeing: “On the delivery rating, I’d add that two of the three late projects changed scope after kickoff. I’ve attached the change log, and I’d like to discuss whether the rating should reflect that.”

Self-performance review examples

The self-review is the most-skipped part of the process and often the most revealing, because the gap between how someone rates their own year and how their manager saw it is where the real conversation lives. A strong self-review is neither self-promotion nor self-flagellation. It anchors to a real moment and a genuine change.

Weak: “I’m a hard worker who communicates well and takes initiative.” Strong: “I underestimated the Q2 migration by three weeks because I didn’t flag the dependency early enough. Next time I’ll raise blockers the day I notice them.”

The second version names something specific enough to be believable and commits to an actual change, which is what makes a self-review worth reading. If you’re writing your own, these 30 self-evaluation examples are sorted by the question on the form.

How to write your own

Here’s the real limit of every list like this one, including this one: the comments that matter are about your actual colleagues, and those aren’t on any page. What you can take is the pattern. Every strong example above follows the same shape: a specific moment, its effect, and for growth areas, the one change that would help. For more raw material in that shape, strengths and areas of improvement examples lists 30 of them, grouped by competency.

That pattern is exactly what a structured 360 round front-loads. When the people around someone are already writing specific, anchored comments instead of trading vague praise, the annual review becomes a synthesis job instead of a blank page. 360 feedback examples shows what that specific version looks like across peer, manager and self feedback.

Picture a manager sitting down to write reviews for eight people and reaching for “meets expectations, solid contributor” for the third time in an hour. That line comes from exhaustion more than laziness: generic is what happens when there’s no fast way to recall the specific thing each person did. A longer bank of performance review phrases won’t fix that. Keeping the specific moments attached to the person all year, in notes or in written 360 feedback, will, because the review then becomes a synthesis of real material.

The comment is only as good as the moment behind it

Good performance review comments come from pointing at something real: an actual moment, its actual effect, and for growth areas, the one thing worth changing. Then resist the urge to smooth it back into a label everyone already uses. Every example above is the same pattern applied to a different competency. Learn the pattern and you won’t need a phrase bank again, because you’ll be able to write the specific, occasionally uncomfortable, genuinely useful line for whatever situation is in front of you.

If you’d rather build that habit year-round instead of reconstructing it at review time, you can start your first 360 in Lynxify.me with no annual contract, set up in about fifteen minutes, and the written responses stay attached to the ratings instead of getting flattened into a number. Or keep a running note by hand. Either way, the habit matters more than the tool.

Frequently asked questions

What do you write in the final comment on a performance review?

Name the one or two things that mattered most this period, the effect they had, and the one focus for the next period. A weak final comment reads like a job description: “meets expectations, good team player.” A useful one points at a specific contribution and a specific area to grow, each tied to something that happened. If you can’t picture the exact moment behind a line, the line isn’t ready yet.

How do I write good performance review comments?

Anchor every comment to a specific moment and its effect, then, for growth areas, add the one change that would help. Skip character labels like “proactive” or “disorganised” and describe the behaviour instead. The test: could this comment apply to more than one person on the team? If yes, it needs a real example attached before it’s useful to anyone.

What are examples of quality of work comments?

A useful quality of work comment names what the person checks or catches and what that saves. For example: “Reviews their own pull requests against the edge-case list before asking for review, so reviewers spend their time on design questions instead of typos.” For a growth area: “The same two fields in the monthly report have needed correcting three months running; a two-minute check before sending would catch them.”

What are examples of quantity of work in a performance review?

Quantity of work is output: how much gets finished in a period. A specific comment ties it to a number the team already tracks, such as “closed 40 support tickets a week through Q3 while keeping the reopen rate under 5%”. A growth-area example: “Has six tasks in progress and two finished this sprint; finishing before starting the next one would move more work to done.”

What is the difference between quality of work and productivity in a review?

Quality of work is how good the output is: accuracy, thoroughness, how often it needs rework. Productivity, or quantity of work, is how much gets done. Keep them in separate comments. A review that judges one by the other is unfair to the person who is slow and right, and lets the person who is fast and sloppy off the hook.

What can an employee write in the final comments of their own appraisal?

Use the space to add context the review missed, agree on next steps, or respectfully disagree with a rating, always with a specific example. For instance: “I agree with the focus on estimating. On the delivery rating, I’d add that two of the three late projects changed scope after kickoff; I’ve attached the change log.” Keep it factual and short.

How do you write a performance review summary?

Group the specific comments into two or three themes, strengths and growth areas, and keep a concrete example attached to each theme. A summary that says “communication came up a few times” has thrown away the useful part. A summary that says “three separate examples point to the same pattern: updates arrive after the deadline has slipped” gives the person something to act on.

DS

Dmytro Shtapauk

The Lynxify.me team writes about building better feedback processes, performance reviews, and people-first HR for growing teams.

Keep reading

Newsletter

Get better in people management

Practical tips and experience from top-notch experts

Thanks! Check your inbox.

You're on the list.