Most performance reviews fail not because managers lack insight, but because they lack language. A manager may have a clear sense of where an employee is struggling — but struggle to articulate it in a way that is specific enough to be useful, fair enough to be defensible, and constructive enough to actually drive improvement. The phrases you use in a performance review determine whether the conversation produces clarity and development or confusion and defensiveness. This guide gives you 150 phrases across the competencies that matter most, organized by rating level, so you can walk into any review with language that is honest, specific, and actionable.

Communication

Exceeds Expectations

• Communicates complex technical information in terms that non-technical stakeholders can act on — without simplifying to the point of inaccuracy.
• Proactively updates stakeholders on project status before they need to ask, and flags issues early enough for course correction.
• Tailors their communication style to the audience with precision: concise in writing, thorough in high-stakes verbal briefings, approachable in peer conversations.
• Written deliverables are consistently clear, well-structured, and require minimal revision before distribution.
• Facilitates team discussions in a way that ensures all voices are heard, decisions are clearly articulated, and next steps are documented.

Meets Expectations

• Communicates progress and blockers clearly during team meetings and one-on-ones.
• Written communication is professional, organized, and generally easy to follow.
• Responds to messages and requests within the expected timeframe.
• Keeps the team informed about developments that affect shared work.
• Presents information at an appropriate level of detail for the context.

Needs Improvement

• Important updates are often communicated late or inconsistently, leaving stakeholders without the information they need to make decisions.
• Written communication frequently requires clarification or revision before it can be used by the intended audience.
• Does not adjust communication style to the audience — what works in a technical peer discussion does not work in a client presentation or an executive briefing.
• Tends to escalate issues only after they have become problems rather than flagging early signals when intervention would be easier.
• Meeting contributions are infrequent or unclear, which limits the team’s ability to benefit from their perspective.

Problem-Solving and Critical Thinking

Exceeds Expectations

• Approaches ambiguous problems by mapping the variables, acknowledging uncertainty, and proposing multiple options with clear tradeoffs — rather than defaulting to the most familiar solution.
• Consistently identifies root causes rather than addressing symptoms, which prevents the same issues from recurring.
• Brings creative solutions to challenges that others have accepted as fixed constraints.
• Anticipates downstream consequences of proposed solutions and designs for them proactively.
• Uses data and evidence to validate assumptions before committing to a direction.

Meets Expectations

• Solves problems within their domain effectively and seeks guidance appropriately when encountering problems outside it.
• Approaches challenges methodically and documents their reasoning in a way that others can follow.
• Evaluates options before committing to a solution rather than acting on the first idea.
• Learns from setbacks and does not repeat the same errors.
• Applies prior experience to new problems with reasonable judgment.

Needs Improvement

• Tends to treat symptoms rather than root causes — the same underlying issues recur because the first-order fix is applied without deeper investigation.
• Problem-solving approach often relies on familiar patterns rather than engaging with the specific features of the current situation.
• Escalates problems that could be resolved independently, or attempts to resolve problems independently that require escalation.
• Proposed solutions frequently introduce new complications that weren’t considered during the planning phase.
• Decisions are sometimes made without sufficient data or consultation with those affected.

Ownership and Accountability

Exceeds Expectations

• Takes full ownership of outcomes — including those that did not go as planned — and leads the recovery effort without waiting to be asked.
• Follows through on commitments reliably, even as priorities shift and conditions change.
• Holds themselves to a higher standard than their role requires, consistently identifying opportunities to contribute beyond their defined scope.
• Acknowledges mistakes quickly, focuses on solutions rather than explanations, and uses setbacks as learning opportunities.
• Creates accountability structures for the team that make commitments visible and failures to deliver easy to address constructively.

Meets Expectations

• Follows through on commitments and flags in advance when a deadline is at risk.
• Takes responsibility for their work product, including errors, without excessive deflection.
• Manages their workload without requiring significant management oversight.
• Seeks clarification when expectations are unclear rather than proceeding on assumptions.
• Prioritizes effectively and delivers the most important work within available time.

Needs Improvement

• When commitments are missed, the response is often focused on explaining why rather than on how to recover and prevent recurrence.
• Tasks assigned without explicit follow-up are at elevated risk of slipping through, indicating that an external accountability system is required where internal accountability should be sufficient.
• Scope of ownership tends to be narrowly interpreted — adjacent issues that clearly fall within the spirit of the role are often deferred or escalated rather than owned.
• The quality of output varies in ways that suggest inconsistent personal standards rather than circumstances outside the employee’s control.

Collaboration and Teamwork

Exceeds Expectations

• Consistently makes the team more effective: shares information proactively, surfaces blockers that affect others, and volunteers for work that fills gaps.
• Builds strong relationships across functional boundaries, which creates informal networks that speed up problem-solving.
• Handles disagreement constructively — advocates for their perspective with evidence, listens carefully to the opposing view, and changes their mind when persuaded.
• Invests in colleagues’ development by sharing knowledge, offering to review work, and providing feedback that is specific and useful.
• Is sought out by peers for input, which reflects the quality of their judgment and the strength of their working relationships.

Meets Expectations

• Contributes effectively in team settings and supports colleagues when asked.
• Shares information that others need without requiring prompting.
• Handles disagreements professionally and works toward resolution rather than escalating conflict.
• Participates in collaborative work as a full contributor.
• Acknowledges others’ contributions and builds on their ideas constructively.

Needs Improvement

• Tends to work in isolation in ways that limit the team’s visibility into their progress and create coordination challenges.
• Disagreements occasionally escalate rather than resolve, which affects team cohesion and creates downstream friction on shared work.
• Does not consistently share information or context that would help colleagues work more effectively.
• Peer relationships are functional but limited in depth, which constrains the informal knowledge-sharing that makes teams most effective.

Technical Skills and Quality of Work

Exceeds Expectations

• Produces work that consistently exceeds quality standards without requiring rework — the first version is typically the version that ships.
• Technical knowledge is deep enough to recognize the limits of available approaches and identify when novel solutions are warranted.
• Actively stays current on developments in their domain and brings new methods or tools that improve the team’s capabilities.
• Deliverables are not only accurate but anticipatory — they address questions the requester hadn’t yet thought to ask.
• Maintains quality standards under deadline pressure in a way that others in the same conditions do not.

Meets Expectations

• Work meets the quality standards expected for the role and requires normal levels of review and revision.
• Technical knowledge is sufficient for the role’s requirements and is kept reasonably current.
• Delivers work that is accurate, complete, and appropriately formatted for its intended use.
• Makes sound technical judgments within their area of expertise.

Needs Improvement

• Output quality is inconsistent in ways that suggest insufficient self-review before submission.
• Technical gaps in one or more areas are affecting the quality of deliverables and the time required for review and correction.
• Rework is required more frequently than the role or the team’s workflow can sustainably absorb.
• Does not consistently apply the standards and conventions established for the role’s work product.

Adaptability and Resilience

Exceeds Expectations

• Maintains effectiveness when priorities shift rapidly, and adjusts their approach without requiring significant management support to reorient.
• Responds to setbacks with analysis rather than discouragement, and is typically the person helping the team regroup after a difficult period.
• Actively seeks out change and ambiguity as development opportunities rather than sources of discomfort.
• In highly uncertain situations, creates clarity for the team where others create more confusion.

Meets Expectations

• Handles changes to priorities or scope without significant disruption to their work or their team’s work.
• Recovers from setbacks in a reasonable timeframe and without extended impact on performance.
• Maintains consistent performance through normal organizational change and uncertainty.

Needs Improvement

• Changes in priorities or unexpected setbacks have a disproportionate effect on performance and morale that extends beyond the change event itself.
• Prefers established routines and clear structure to a degree that limits effectiveness in the inherent ambiguity of the role.
• Recovery from difficult projects or feedback takes longer than the team can accommodate at current pace.

Leadership and Influence (for Individual Contributors in Senior Roles)

Exceeds Expectations

• Shapes the team’s direction through the quality of their thinking rather than through formal authority.
• Mentors junior colleagues with deliberate investment — not just answering questions, but building understanding and capability.
• Influences decisions above their formal level by earning credibility through track record and by presenting ideas with compelling evidence and clear reasoning.
• Creates conditions in which others do their best work — by removing obstacles, sharing context, and advocating for their needs.

Meets Expectations

• Shares expertise willingly and contributes to the development of less experienced colleagues.
• Influences peer decisions constructively and is open to being influenced in return.
• Represents the team’s perspective appropriately in cross-functional settings.

Needs Improvement

• Has not yet found the right operating mode for influence at this level: either too deferential to have real impact on important decisions, or too forceful in a way that creates resistance.
• Development of junior colleagues is inconsistent and tends to be reactive rather than intentional.
• Credibility in cross-functional settings has not yet reached the level the role requires.

People Leadership (for Managers)

Exceeds Expectations

• Builds teams that are stronger than the sum of their individual parts — by creating the conditions for collaboration, investing in each person’s growth, and maintaining clarity about goals and roles.
• Feedback from direct reports consistently indicates that they feel supported, challenged, and clear about expectations.
• Develops successors: employees who have grown under this manager into roles of significantly greater responsibility.
• Navigates difficult performance conversations with honesty and care — employees who receive hard feedback from this manager typically feel respected rather than diminished.
• Retains strong performers at above-average rates through the quality of their management relationships and the development opportunities they create.

Meets Expectations

• Direct reports are generally clear on their goals and receive regular, constructive feedback.
• Team morale and engagement are at healthy levels, reflecting a positive management relationship.
• Performance issues are identified and addressed in a timely manner with appropriate support.
• One-on-ones are regular, well-prepared, and useful for direct reports.

Needs Improvement

• Team members have varying levels of clarity about their goals and how their work connects to broader priorities.
• Feedback to direct reports tends to be either infrequent, overly general, or concentrated at review time rather than delivered in the moment when it would be most actionable.
• Performance issues are addressed later than the employee’s development trajectory and team morale can absorb.
• One-on-ones are valuable but inconsistently prepared, which limits their impact on individual development.

How to Write a Complete Performance Review Using These Phrases

Start With a Summary Observation

Open each review section with a sentence that orients the employee to your overall assessment of the dimension before the specific language: “This year, your communication has been one of your clearest areas of strength — I’ll describe why below.” or “Communication is the dimension where I see the most room for development, and I want to walk through what I’ve observed.” The summary primes the employee to receive the detailed feedback rather than decoding as they read.

Follow With Two or Three Specific Examples

Take the phrase that best describes the employee’s performance level on each dimension, then immediately follow it with a specific example from the review period. The phrase describes the pattern; the example makes it real and unchallengeable. “Consistently delivers work that requires minimal revision — for example, the Q4 budget model was used as submitted without changes, which saved the finance team two full days of back-and-forth.”

Close With a Development Direction

End each dimension with a directional statement about what you want to see change or continue. For Exceeds ratings: “I want to help you build on this strength in the coming year by putting you in contexts where it can have even broader impact.” For Needs Improvement ratings: “The specific behavior I want to see shift is [X]. Here is what that would look like in practice and why it matters.” This closes the loop between evaluation and development and connects the review to the goal-setting conversation that should follow it.

Phrases to Avoid in Performance Reviews

Certain types of language reduce the quality of performance reviews regardless of the underlying assessment. Avoid:

• Trait language: “He is lazy,” “She has a bad attitude.” Describe the behavior, not the trait.
• Vague superlatives: “An outstanding employee,” “Always a pleasure to work with.” These are not evaluative.
• Recency language: “Lately” or “recently” signals that you are evaluating a short window rather than the full period.
• Comparative language: “Better than most of the team” or “Doesn’t work as hard as [name].” Evaluate against role standards, not against peers.
• Hedged negatives: “Could perhaps be more proactive about communication.” If communication is a genuine development area, name it clearly.

For a deeper treatment of how to structure the full review process, see our guide to writing performance reviews, and for conducting the actual conversation effectively, see two-way dialogue in performance reviews.

Frequently Asked Questions About Performance Review Phrases

Key Takeaways

Strong performance review phrases are specific, behavioral, and connected to real observations. They describe what the employee does — not what they are — and they leave the employee with a clear picture of what “better” looks like in practice. Use these 150 phrases as a starting structure, then make each one your own by grounding it in specific incidents from the review period. The goal of every phrase is not documentation for its own sake — it is a conversation starter that helps the employee understand where they are, why it matters, and what comes next.