A phrase bank gets you past a blank page, but a bare phrase makes a weak review. Use these as starting points, then add the specific example that makes each one true.
Every phrase below becomes more useful if you add three things: a specific example, what the impact was, and what you want next. “Flags risks early” is a start. “Flagged the vendor delay two weeks before the launch date, which let us move the demo” is a review.
Where a phrase does not match what you saw, do not use it. A generic phrase that is slightly off does more damage than a blank line, because the person knows it was not written about them.
A formula for any phrase
Situation: where and when this happened.
Behavior: what they did, in observable terms.
Impact: what changed as a result.
Next: what you would like more of, or different, from here.
Communication
Strengths
Explains complex topics in terms the audience can act on.
Flags risks early, with options attached, rather than waiting to be asked.
Writes status updates that others can read without a follow-up meeting.
Listens fully before responding and restates the point to check understanding.
Development areas
Updates tend to arrive after a decision has already been made. Sharing the draft earlier would let others weigh in.
Gives long answers when a short one would do. Leading with the conclusion would help the reader.
Disagrees in the moment but not in the channel where the decision is recorded.
Messages are sometimes read as more blunt than intended. Adding the reason behind a request would soften that.
Collaboration
Strengths
Makes it easy for others to build on their work by documenting assumptions.
Credits colleagues publicly and by name.
Takes on unglamorous work when the team needs it, without keeping score.
Asks for help early and is generous when others ask them.
Development areas
Tends to solve problems alone before involving others, which has led to duplicated effort.
Reviews and feedback on others’ work are often brief. More explanation of the why would make them easier to act on.
Can be slow to hand over context when work moves to someone else.
Has a strong view of the right approach and does not always leave room for alternatives.
Ownership and reliability
Strengths
Follows work through to the outcome, not just to the handoff.
Commitments can be relied on. When one is at risk, they say so before the date.
Notices the gap nobody owns and closes it.
Treats mistakes as information: acknowledges them, fixes them and shares what changed.
Development areas
Several commitments this cycle were met late without notice. Raising the slip earlier is the main change to make.
Takes on more than can be delivered and does not renegotiate until the deadline is near.
Tends to consider a task done when it is shipped, rather than when it works for the user.
Needs prompting on follow-ups that were agreed in meetings.
Quality and craft
Strengths
Work arrives well checked, and reviewers rarely find surprises.
Pays attention to the edge cases others skip.
Improves the surrounding system while doing the task, not only the task.
Sets a standard that colleagues copy.
Development areas
Output is fast but would benefit from a self-review pass before it reaches others.
Recurring small errors in the same area suggest a checklist would help.
Spends longer than the value warrants on finishing touches. Agreeing what “good enough” means up front would help.
Needs to document decisions so the reasoning survives after they move on.
Leadership and influence
Strengths
Gives people context, not only tasks.
Raises the bar for the team without making individuals feel judged.
Delegates in a way that stretches people and is available when they get stuck.
Takes responsibility for the team’s results, including the ones that went wrong.
Development areas
Tends to step in and do the work rather than coach, which limits others’ growth.
Gives feedback mostly at review time. More frequent, smaller feedback would be easier to absorb.
Decisions are sometimes made without explaining the reasoning, so the team has to guess.
Avoids hard conversations until the problem is large.
Growth and learning
Strengths
Asks for feedback and acts on it visibly.
Picked up a new area quickly and is now a go-to person for it.
Shares what they learn through short write-ups or demos.
Takes on stretch work and is honest about where they are still learning.
Development areas
Has not yet moved beyond the first area they learned. A defined stretch goal would help.
Receives feedback calmly but changes are not always visible afterwards. Checking in on one agreed point each month would help.
Tends to wait for direction on development instead of proposing it.
Has the skills for the next level but is not yet doing the next level’s work consistently.
Words and patterns to avoid
Some phrases read as feedback but carry no information, or carry bias. Replace them with behavior.
“Great attitude”, “not a culture fit” or “lacks passion”: these describe a judgment, not an observation. Say what they did.
“Abrasive”, “bossy”, “emotional”: trait labels that are applied unevenly across people. Describe the specific interaction.
“Always” and “never”: almost always inaccurate, and invite argument over the exception.
“Meets expectations” alone: say which expectations, and how you know.
Comparisons with colleagues by name: they belong in calibration, not in the person’s own review.
FAQ
Frequently asked questions
Can I copy these performance review phrases directly?
You can, but they work best as a starting point. Add the example, the impact and the next step. A review made only of stock phrases is easy to spot and gives the person nothing to act on.
How do I write negative feedback kindly?
Be specific and factual, name the impact, and say what you want instead. Kindness comes from the clarity and the offer of support, not from softening the message until it disappears.
How many strengths and development areas should a review have?
Two or three of each. If you list ten development areas, none of them will get attention. Pick the ones that matter most for the role over the next period.
Are performance review phrases appropriate for self-assessments too?
Yes, with the order reversed: start from your own examples and use a phrase only if it describes what you did. Self-assessments are also stronger with evidence such as dates, outcomes and numbers.
Where review.center fits
In review.center, the written comments on each category come from the reviewers and the manager, and the system can draft improvement points from them. Those points are checked again next cycle, so a development phrase becomes something that is followed up on rather than something that was written once.