150 Performance Review Phrases (Ready to Use)

What are performance review phrases?

Performance review phrases are structured, behavior-based descriptions used in employee evaluations to describe patterns of performance. The best phrases are specific enough to be meaningful, general enough to apply to multiple employees, and behavioral rather than character-based. Use these as starting points — always add a specific example.

Writing 12 individual reviews in one sitting is hard. The quality degrades by review 8 because you've run out of ways to say the same things. This list is designed to be practical: 150 phrases, organized by skill category and rating direction, ready to copy and adapt.

Communication skills

Exceeds expectations

Communicates complex ideas in a way that non-experts can understand and act on.
Proactively shares context across teams, preventing duplicate work and misaligned assumptions.
Written communication (docs, Slack, email) is consistently clear, concise, and actionable — rarely requires clarification.
Delivers difficult feedback in a way that is direct and constructive, without avoiding the core message.
Adapts communication style effectively to different audiences — technical deep-dives with engineers, executive summaries with leadership.
Actively listens in meetings — asks clarifying questions, paraphrases to confirm understanding, and contributes only after others have been heard.

Meets expectations

Communicates progress and blockers clearly to the team and manager.
Written documentation is readable and covers the relevant context for the intended audience.
Participates constructively in team discussions and contributes relevant points.
Gives feedback that is actionable, even if delivery could be more direct at times.

Needs development

Would benefit from providing more proactive updates — the team often learns about blockers after they've affected timelines.
Written communication sometimes requires multiple back-and-forth messages to resolve ambiguity; working toward a "complete on first read" standard would improve speed.
Tends to communicate well in 1:1s but less consistently in group settings; more participation in team discussions would increase visibility and impact.

Collaboration and teamwork

Exceeds expectations

Consistently puts team outcomes ahead of personal credit — colleagues cite this as one of the team's cultural strengths.
Actively unblocks teammates, volunteering time and context without being asked.
Builds strong cross-functional relationships that make projects move faster — has established trust with [function] and [function] that reduces friction on shared work.
Contributes to a psychologically safe team environment by welcoming questions, admitting uncertainty, and not penalizing mistakes.
Takes on team-health work (documentation, mentorship, process improvements) that doesn't show up in output metrics but has an outsized impact on the team's effectiveness.

Meets expectations

Works effectively with teammates and contributes to a positive team dynamic.
Fulfills cross-functional commitments reliably — colleagues can depend on agreed deliverables arriving on time.
Handles disagreements professionally, engaging with other viewpoints before advocating for their own.

Needs development

Tends to work independently on problems that could be solved faster with input from the team; bringing others in earlier would accelerate outcomes.
At times, disagreements with collaborators escalate rather than converge; developing an approach that acknowledges other perspectives before defending a position would improve cross-team relationships.

Problem-solving and critical thinking

Exceeds expectations

Identifies root causes rather than symptoms — solutions address the underlying problem, not just the visible one.
Brings well-reasoned tradeoff analysis to decisions, making it easier for stakeholders to choose with confidence.
Anticipates downstream consequences of decisions, raising relevant concerns before they become problems.
Comfortable operating with ambiguity — makes reasonable progress on under-defined problems rather than waiting for complete clarity.
Brings creative solutions to problems that initially appear to have only expensive or low-quality options.

Meets expectations

Approaches problems methodically and finds effective solutions within the expected timeframe.
Escalates appropriately when a problem exceeds their capacity or authority — doesn't block on decisions they should surface.
Considers more than one option when tackling a problem, even if the first option is ultimately selected.

Needs development

Would benefit from a more structured approach to problem diagnosis — recent incidents showed solutions applied before root causes were confirmed.
Tends to escalate quickly on problems that could be resolved independently; building more confidence in unblocking at the right scope would increase effectiveness.

Leadership and ownership

Exceeds expectations

Owns outcomes, not just tasks — follows through until the result is achieved, not just until the deliverable is submitted.
Leads by influence across organizational lines, getting buy-in without formal authority.
Actively develops teammates — shares knowledge, gives feedback, and creates opportunities for others to grow.
Makes decisions at the right scope — doesn't require approval for decisions within their authority, and appropriately elevates those that aren't.
Identifies gaps and fills them without waiting to be assigned — organizational health is measurably better because of this.
Models the standards expected of the team in their own work — the team calibrates against their behavior.

Meets expectations

Takes clear ownership of assigned areas and follows through reliably.
Appropriately leads discussions and decisions in their area of expertise.
Contributes to the team's effectiveness as an individual contributor while showing early signals of broader leadership.

Needs development

Often seeks reassurance before acting on decisions within their scope; building confidence in acting on their own judgment within defined boundaries would increase velocity.
Would benefit from taking on more visible ownership of a project end-to-end to develop the full accountability and coordination skills expected at the next level.

Technical skills / role-specific execution

Exceeds expectations

Delivers work that meets the bar for the next career level — quality, scope, and complexity are consistently above expectations for current level.
Technical or domain knowledge depth is a resource for the team — colleagues seek out their expertise when solving hard problems in this area.
Proactively improves tooling, processes, or systems beyond the immediate task — the downstream work is better for it.
Maintains quality under pressure — output doesn't degrade significantly when timelines are compressed.

Meets expectations

Executes assigned work to the expected quality standard within the expected timeframe.
Demonstrates solid command of the tools and practices required for the role.
Output is reliable — can be counted on to deliver what was agreed.

Needs development

Output quality is inconsistent — some work is excellent, others require significant revision; developing a more reliable quality check process before handoff would reduce rework.
Technical gaps in [specific area] are limiting the scope of projects they can contribute to independently; a development focus here would unlock the next level of contribution.

Goal achievement and results

Exceeds expectations

Consistently delivers on commitments and often exceeds the original target — the gap between what they commit to and what they achieve is positive.
Contributes to team outcomes beyond their individual goals — the team's aggregate results are better because of their involvement.
Sets ambitious goals and reaches them through disciplined execution rather than sandbagging.

Meets expectations

Achieves the majority of committed goals within the review period, with clear progress on the remainder.
Reprioritizes effectively when goals shift — adjusts execution without losing track of core commitments.

Needs development

Goal completion rate has been below expectations this period; working with the manager to diagnose whether this is a capacity, priority, or estimation issue would clarify the path forward.
Goals are sometimes written too broadly to measure at end-of-period; working toward more specific, measurable targets at the planning stage would make achievement clearer.

Growth mindset and learning

Exceeds expectations

Treats feedback as data — integrates it quickly, without defensiveness, and applies it visibly.
Actively seeks out learning beyond the immediate job requirements, which shows up as a broader skill set than peers at the same level.
Learns from failures constructively — diagnoses what happened and changes approach, without excessive self-criticism or blame-shifting.

Meets expectations

Responds well to feedback and shows improvement over time in areas where development was requested.
Engages with learning opportunities when they're made available.

Needs development

Feedback from the previous review period has not been fully applied; re-visiting the development areas together and setting concrete indicators of progress would help.
Tends to defend approaches when challenged; building a practice of asking "what would change my mind?" before responding to feedback would accelerate growth.

How to use these phrases effectively

Each phrase in this list is a starting point, not a finished sentence. To make a phrase credible in a review:

Pick the phrase that best matches the behavior you observed.
Anchor it to a specific example from the review period — even one sentence: "as shown when..."
State the impact where relevant: "which meant the team could..."
Avoid stacking 6 similar phrases — pick the 2–3 that are most true and most impactful.

For Harmny users: Org Brain can draft performance review summaries based on your 1:1 notes, goal completion data, and previous ratings — reducing the blank-page problem significantly. See performance reviews.