360 feedback examples: what strong feedback looks like
Read more Questions & Templates
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 with 100 or more phrases, sorted by competency, split into positive and constructive. They’re not wrong, exactly. They’re just generic by construction, built to apply to anyone, which means they help no one in particular. One competitor’s own advice tells readers to “partner these phrases with real examples” and then hands over 118 phrases with not one real example attached. That’s the gap in the sharpest terms available: even the people writing the lists know specificity is the answer. They just don’t do it. This piece does, for a handful of the competencies that come up most, with the weak version next to the strong one 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.
- Positive comments fail the same way constructive ones do: staying generic. A vague compliment gives the person nothing to repeat on purpose.
- The move that makes a growth area receivable is naming the behaviour and its consequence, then pointing forward, never the character label.
- A performance review summary should group comments into themes without stripping out the examples that earned them. “Communication came up” helps no one; the example behind it does.
- 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.
There’s a simple test: could this comment apply to more than one person on your team? If yes, it’s a label, not feedback. “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, not the day before standup,” names an actual behaviour and lets the reader picture it. That’s the whole difference, and it’s not unique to annual reviews either; why 360 feedback is always vague covers the same failure mode in multi-rater rounds. Every example below follows the same shape: a specific action, its effect, and for growth areas, the one change that would help.
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 after a deadline has already slipped, not before, 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.
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, not 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.
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 actually 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.
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 instead of adversarial.
The summary 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 summary: “Communication was mentioned as an area to work on.” A useful summary: “Three separate people independently described the same pattern: updates land after a deadline slips, not before. That’s specific enough to fix.”
The rule is simple: no theme without the example that earned it. Group the comments, but keep at least one concrete instance attached to each theme rather than replacing it with a label. A summary is a way into the specifics, not a substitute for them.
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 isn’t self-promotion or 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 surface blockers the day I notice them, not the day they become unavoidable.”
The second version does two things the first can’t: it names something specific enough to be believable, and it commits to an actual change rather than a general virtue. That’s what makes a self-review worth reading rather than skimming.
Here’s the honest 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, not the sentences. Every strong example above follows the same shape, a specific moment, its effect, and for growth areas, the one change that would help.
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. And if writing comments like these by hand for six or more people every review period is what’s eating your afternoons, choosing performance review software covers what’s actually worth paying for versus what you can keep doing manually.
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 isn’t lazy so much as exhausted, generic is what happens when there’s no fast way to recall the specific thing each person did. The fix isn’t a longer bank of performance review phrases. It’s keeping the specific moments attached to the person all year, in notes or in written 360 feedback, so the review is a synthesis of real material instead of a blank page at deadline.
Good performance review comments aren’t a matter of finding better words. They’re a matter of pointing at something real, an actual moment, its actual effect, and for growth areas, the one thing worth changing, then resisting 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 actually 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, no annual contract, no credit card required, 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.
What should I write in my overall comment for a performance review?
Name the one or two things that mattered most this period and the effect they had, not a summary of every task. A weak overall comment reads like a job description: “meets expectations, good team player.” A useful one names a specific contribution and a specific area to grow, each anchored to something that actually 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 positive comments in a performance review?
A useful positive comment names a specific action and its impact. Weak: “great communicator.” Specific: “sends a short written recap after every client call, so nothing said gets lost or misremembered a week later.” The specific version tells the person exactly what to keep doing, which is the entire point of a positive comment. A generic compliment, however warm, gives them nothing to repeat on purpose.
How do you write a performance review summary?
Group the specific comments into two or three themes, strengths and growth areas, and keep the concrete examples attached to each theme rather than replacing them with a label. 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 land after the deadline, not before” gives the person something to act on.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
