Most Performance Review Phrases Are Vague Enough to Mean Nothing. Here Are 150 That Aren't.

You sat down to write a review, opened a phrase list, and thirty minutes later you have a draft full of sentences like “consistently demonstrates strong work ethic” and “is a valued team contributor.” You know the document is bad. You also do not know how to make it better, because the phrases you copied looked professional in the list and looked like vapor on the page.

The problem is not that you are using a phrase list. The problem is that most phrase lists are written to sound formal, not to be specific. They give you sentences that fit any employee in any situation, which is exactly why they fail to describe any specific person doing any specific work. The fix is not to throw the list away. The fix is to use phrases that come with their own customization built in.

This is a cluster article inside a larger guide. If you have not read it yet, the complete pillar guide on performance reviews covers the full system: prep timeline, the 60-minute conversation framework, rating bias, and follow-through. This page is the practical phrase library you can pull from while you write the actual document.

What follows is 150 phrases organized across 10 competencies. Each one is written with a bracket telling you exactly what to fill in. If you cannot fill in the bracket with something specific, that is your signal that the phrase does not belong in this review yet. At the end you will also find five phrases to retire from your vocabulary entirely, plus a quick framework for taking any phrase from “generic” to “specific to this person, this cycle.”

How to use this list (in 90 seconds)

1. Find the competency that matches what you are writing about. Skim the three tiers (above expectations, meets expectations, growth needed) and pick the one that honestly fits this person’s cycle.
2. Pick a phrase that fits the situation, not the rating. The phrase is the structure. You still have to fill it in.
3. Replace every bracketed item with a specific example, number, name, project, or metric. If you cannot, do not use that phrase. Pick another or write your own.
4. Read the sentence aloud. If you would not say it across a table to this person, rewrite it.

If a planned tool would help you scope how many hours this work will actually take, the Performance Review Time Calculator gives you a realistic estimate based on your team size and review depth. The number is usually higher than people expect, which is why most reviews get rushed.

A note before you copy anything

Research from the NeuroLeadership Institute on performance management consistently finds that the biggest predictor of whether a review changes someone’s behavior is not the rating. It is the specificity of the language used to describe what happened. A vague “above expectations” rating with vague phrases lands as nothing. A “meets expectations” rating with specific evidence often lands harder than a higher rating with cliches.

The phrases below are written so the structure forces specificity. The brackets are not optional decoration. They are the work.

1. Outcomes and results (15 phrases)

This is where most reviews start, and where most reviews fail. The trap: confusing what someone delivered with how loud they talked about delivering it. If you cannot quote a number, an outcome, or a specific shipped artifact, you are rating visibility, not results.

Above expectations:

1. Delivered [specific project] [N] weeks ahead of plan, with [specific impact metric] beyond the original scope.
2. Owned [specific outcome] end-to-end, including [specific stretch element], without needing escalation when [specific blocker] surfaced.
3. Reframed [specific goal] mid-cycle when [specific change] occurred, and still hit [revised target] within the original window.
4. Generated measurable lift in [specific metric], moving it from [baseline] to [actual] against a target of [target].
5. Picked up [specific work owned by another role] when [specific situation] emerged, while still hitting their own committed deliverables.

Meets expectations: 6. Delivered [specific project] within the agreed-upon timeline and quality bar. 7. Hit [specific target metric] for [time period], in line with the cycle plan. 8. Closed out [N] [recurring deliverables] with consistent quality across the cycle. 9. Met every commitment made in [specific planning ritual] without missed deadlines. 10. Carried [specific recurring responsibility] reliably across [time period], freeing the team to focus on [specific work].

Growth needed: 11. Missed the deadline on [specific deliverable] by [specific length of time], without surfacing the risk early enough to adjust scope or staffing. 12. Hit [specific output metric] but at the cost of [specific quality or relationship metric], suggesting we need to recalibrate how we measure success on this work. 13. Started [N] initiatives during the cycle and closed [smaller N], with [specific deliverable] remaining open at cycle end. 14. Delivered [specific output] but the result did not move [target metric] in the way the plan assumed, suggesting the goal itself needs to be revisited together. 15. Required [specific level of intervention] from me to land [specific deliverable] that should have been within their independent scope.

Before: “Sarah did a great job on her projects this quarter.” After: “Sarah delivered the customer-onboarding redesign two weeks ahead of plan, reducing time-to-first-value from 21 days to 12 days against a target of 14, the largest single-quarter movement on the team’s key result list this year.”

2. Quality of work (15 phrases)

Quality is the competency where managers most often confuse “I would not have done it that way” with “the work was not good.” Be specific about the standard you are evaluating against, and where the work landed against it.

Above expectations:

1. Produced [specific artifact] that exceeded the team’s quality bar, specifically in [specific dimension: accuracy, completeness, clarity, robustness].
2. Caught [specific risk or defect] in [specific work] before it shipped, preventing [specific downstream cost].
3. Raised the team’s standard for [specific aspect of work] by introducing [specific practice or tool].
4. Reviewed [specific work from another teammate] in a way that materially improved [specific quality dimension].
5. Built [specific reusable component] that other teammates have since adopted for [specific use case].

Meets expectations: 6. Produced [specific artifact] at the team’s standard for [specific dimension]. 7. Required minor revisions on [specific work], all addressed within the normal review cycle. 8. Met or exceeded the documentation expectations on [specific deliverable]. 9. Sustained consistent quality across [specific volume] of [recurring work] across the cycle. 10. Adopted feedback on [specific quality dimension] within [specific time window] and applied it to subsequent work.

Growth needed: 11. Shipped [specific deliverable] with [specific defect category] that required rework after the cycle. 12. Showed inconsistency in [specific quality dimension] between [specific work A] and [specific work B], suggesting we need to align on the standard. 13. Tended to mark work as “done” when [specific finishing element] was still incomplete, creating [specific downstream impact]. 14. Did not consistently incorporate review feedback on [specific dimension], with the same category of issue surfacing in [N] subsequent pieces of work. 15. Operated below the team’s quality standard on [specific dimension], which we are going to make the explicit focus of next cycle’s development plan.

Bias warning: If you find yourself writing “quality could improve” without naming a specific dimension, you are rating taste, not quality. Specify what bar and how the work compared.

3. Communication (15 phrases)

Communication is the broadest, most overused word in a review. Break it down: written, verbal, upward, lateral, with stakeholders, in conflict, asynchronously. The phrase has to specify which kind.

Above expectations:

1. Wrote [specific document or proposal] that became the reference everyone returned to during [specific decision].
2. Translated [specific complex topic] for [specific non-expert audience] in a way that unblocked [specific decision or action].
3. Surfaced [specific concern] early enough that we could adjust [specific decision], even though raising it created short-term friction.
4. Ran [specific meeting type] in a way that consistently ended with clearer decisions and shorter follow-up threads.
5. Defended [specific position or recommendation] with evidence in [specific context], including in front of [specific senior stakeholder].

Meets expectations: 6. Communicated [specific kind of update] on the agreed-upon cadence with [specific stakeholders]. 7. Wrote [specific recurring document] at a quality that did not require rework before sending. 8. Asked clarifying questions in [specific context] that prevented misunderstandings on [specific work]. 9. Adjusted communication style appropriately when working with [specific cross-functional team or stakeholder]. 10. Closed loops on [specific kind of request] without prompting, including when the answer was “no” or “later.”

Growth needed: 11. Did not surface [specific risk or blocker] until [specific late point], limiting our options for response. 12. Defaulted to [specific medium, e.g., long Slack threads, in-person conversations] when the situation required [specific other medium, e.g., a written decision document]. 13. Tended to over-communicate volume but under-communicate priority, leaving stakeholders uncertain about which signals to act on. 14. Showed difficulty maintaining tone in [specific kind of conflict or pushback], with [specific incident] as a representative example. 15. Did not adjust written communication for the seniority or context of the audience in [specific specific examples].

4. Collaboration and teamwork (15 phrases)

The trap here is rewarding the person who is most pleasant to be around rather than the person who actually moves the team forward. Pleasantness is not collaboration. Collaboration is what happens when work needs to flow through people.

Above expectations:

1. Made [specific teammate]‘s work materially better through [specific behavior: pairing, review, knowledge transfer].
2. Stepped into [specific situation] when a teammate was [specific constraint: out, overloaded, struggling] and absorbed [specific scope] without dropping their own commitments.
3. De-escalated [specific tension between teammates or teams] in a way that protected the working relationship and the work.
4. Built relationships with [specific cross-functional partners] that compounded into [specific collaboration win] later in the cycle.
5. Mentored [specific peer or junior] through [specific area of growth], with measurable improvement in their work over the cycle.

Meets expectations: 6. Participated reliably in [specific recurring collaboration ritual] without needing prompting. 7. Responded to teammate requests on [specific kind of work] within reasonable time and quality. 8. Shared knowledge on [specific topic] with the team in [specific format: documentation, demo, walkthrough]. 9. Worked productively with [specific cross-functional partner] on [specific deliverable]. 10. Gave constructive feedback in code reviews / draft reviews / design critiques on [specific number] of teammates’ work this cycle.

Growth needed: 11. Created bottlenecks in [specific collaboration point] by [specific behavior: slow review turnaround, holding context, single-threading decisions]. 12. Showed friction with [specific teammate or team] that affected [specific shared deliverable], requiring my involvement to repair. 13. Tended to operate as a solo contributor on work that was meant to be shared, with [specific incident] as a representative case. 14. Did not consistently surface what they were learning in a way that benefited teammates working on similar problems. 15. Disengaged from [specific kind of team ritual or shared work], reducing the team’s overall velocity on [specific area].

5. Initiative and ownership (15 phrases)

Initiative is the competency where managers project the most. Be careful: “did not show enough initiative” can mean “did not behave the way I would have.” Anchor to specific opportunities the person had and whether they took them.

Above expectations:

1. Identified [specific gap or risk] before it surfaced as a problem, and shipped [specific fix] without being asked.
2. Took ownership of [specific ambiguous problem] that did not formally belong to anyone and drove it to [specific outcome].
3. Proposed [specific improvement to a team process] and saw it through to adoption.
4. Volunteered for [specific stretch work] and delivered it at the team’s standard despite operating outside their core area.
5. Reflected proactively on [specific past decision] and adjusted approach for [specific subsequent work].

Meets expectations: 6. Took ownership of [specific defined scope] and operated independently within it. 7. Surfaced [specific blocker] when it appeared and proposed [specific path forward]. 8. Followed through on [specific commitment] without reminders. 9. Owned the resolution of [specific category of issue] without escalation in [specific number] of cases. 10. Asked for stretch work in [specific area] and grew into it appropriately.

Growth needed: 11. Required external prompts to start [specific recurring work] across the cycle. 12. Tended to flag problems without proposing options, leaving the resolution work for me or for [specific other person]. 13. Stayed strictly within their job description on [specific case] when broader ownership would have served the team better. 14. Did not consistently follow through on [specific commitment type] without reminders, with [specific examples] as cases. 15. Showed reluctance to take on ambiguous work, defaulting to “tell me exactly what you want” instead of proposing a path.

6. Problem solving and judgment (15 phrases)

Judgment is hard to evaluate because the inputs to a decision are often invisible months later. Anchor to specific decisions you saw them make, and whether they used the information available at the time well.

Above expectations:

1. Made the call on [specific decision] with incomplete information, and the call held up against subsequent data.
2. Identified the root cause of [specific recurring issue] when previous attempts had treated symptoms.
3. Reframed [specific stuck problem] in a way that opened [specific path] previously not considered.
4. Weighed [specific tradeoff] explicitly with stakeholders, and the decision-making process itself raised the team’s bar for how we approach similar calls.
5. Recognized when [specific approach] was not working and pivoted to [specific alternative] before the cost compounded.

Meets expectations: 6. Made sound calls on [specific category of recurring decisions] within their scope. 7. Escalated [specific kinds of decisions] appropriately, with the right framing and options. 8. Used [specific data source] consistently to inform [specific recurring decision]. 9. Showed appropriate calibration on which problems to handle independently vs. surface up. 10. Diagnosed [specific issue] correctly enough that the fix held.

Growth needed: 11. Tended to debug at the symptom level on [specific kind of issue], with the root cause re-surfacing later. 12. Made [specific decision] without including [specific stakeholder whose input was material], leading to [specific rework]. 13. Optimized for [specific local outcome] on [specific case] in a way that hurt [specific team-level outcome]. 14. Got stuck on [specific class of problem] longer than the team’s norm, without escalating for help. 15. Showed pattern of revisiting [specific decision] multiple times without new information, which slowed [specific downstream work].

7. Adaptability and growth mindset (15 phrases)

Reserve this competency for evidence of actual change, not for personality assessments. “Open to feedback” is not adaptability. Adapting to specific feedback in a specific way is.

Above expectations:

1. Adjusted approach to [specific work] after [specific feedback], with measurable improvement on [specific subsequent deliverable].
2. Picked up [specific new skill or tool] outside their primary area of strength and used it on [specific work] this cycle.
3. Took on [specific role change or responsibility] mid-cycle and grew into it within [specific timeframe].
4. Sought out [specific kind of feedback] from [specific source] and applied it visibly to [specific subsequent work].
5. Recovered from [specific setback or mistake] in a way that made the team better, not just themselves.

Meets expectations: 6. Incorporated review feedback on [specific work] within the next cycle. 7. Adapted to [specific organizational change] without major productivity loss. 8. Picked up [specific new tool or process] required for [specific work]. 9. Asked for feedback on [specific aspect of their work] at appropriate cycle points. 10. Showed a willingness to revisit [specific approach or position] when new information arrived.

Growth needed: 11. Repeated [specific feedback theme] across [N] cycles without observable change in behavior. 12. Showed resistance to [specific shift in approach] that the rest of the team had adopted. 13. Reverted to [specific old pattern] under stress, with [specific incident] as a recent example. 14. Did not consistently seek out feedback in [specific area where they have a known growth edge]. 15. Required multiple repetitions of the same conversation about [specific behavior] before adjusting.

8. Leadership and influence (15 phrases)

Apply this competency at the level appropriate for the role. A junior IC has a different leadership scope than a senior IC, who has a different scope than a tech lead, who has a different scope than a manager. Match the phrase to the role’s actual leverage points.

Above expectations:

1. Influenced [specific decision] through evidence and clear framing, even though they did not have formal authority over the call.
2. Set a tone in [specific recurring forum] that other teammates have explicitly cited as raising the bar.
3. Mentored [specific teammate] through [specific growth edge] in a way that visibly shifted their work.
4. Built credibility with [specific stakeholder group] that the team has been able to draw on for [specific subsequent work].
5. Took an unpopular but correct position on [specific issue] and held it under pushback until the data came in.

Meets expectations: 6. Owned the technical or strategic direction on [specific scope] with appropriate input from the team. 7. Represented the team well in [specific forum] when asked to. 8. Provided thoughtful input on [specific decisions] outside their direct scope. 9. Set clear expectations with [specific collaborators] on [specific work]. 10. Supported [specific peers or juniors] through informal mentoring.

Growth needed: 11. Did not consistently represent the team’s perspective in [specific forum] when given the opportunity. 12. Showed reluctance to take a position on [specific kind of issue] where their judgment was actively needed. 13. Influenced [specific decision] in a way that reflected personal preference more than the team’s broader interests. 14. Defaulted to deference on [specific topic] where the team needed them to push. 15. Underused their credibility with [specific stakeholder] on [specific case] that would have benefited from it.

9. Time management and productivity (15 phrases)

Be careful: “manages time well” is often code for “responds to my Slack messages quickly.” Time management is about throughput on what matters, not appearance of busyness. Anchor to outcomes, not optics.

Above expectations:

1. Sustained high throughput on [specific category of work] across the cycle without compromising on [specific quality dimension].
2. Reorganized [specific recurring time commitment] to free [specific block] for high-leverage work, and used the block.
3. Said no to [specific lower-priority request] in service of [specific higher-priority commitment], with appropriate framing.
4. Cut [specific time sink] from the team’s week by introducing [specific change or tool].
5. Operated at the right level of detail for the task, neither over-investing in low-impact work nor under-investing in high-impact work.

Meets expectations: 6. Met [specific recurring deadlines] consistently across the cycle. 7. Kept [specific number] of parallel workstreams moving at a healthy pace. 8. Estimated time on [specific kind of task] within the team’s norm of accuracy. 9. Used [specific time-management tool or ritual] consistently throughout the cycle. 10. Recognized when their plate was full and surfaced the tradeoffs to me before agreeing to additional work.

Growth needed: 11. Spread attention across too many parallel commitments, with [specific deliverable] suffering as a result. 12. Underestimated time on [specific class of work] consistently across the cycle, by [specific magnitude]. 13. Defaulted to deep-focus work when the situation required quick context-switching, or vice versa. 14. Accepted [specific recurring meeting load] that displaced higher-leverage work without renegotiating. 15. Treated urgency and importance as the same thing, with [specific outcome] suffering because [specific important non-urgent work] kept getting pushed.

10. Customer and stakeholder focus (15 phrases)

This applies whether your “customer” is external (paying users) or internal (other teams who depend on your work). The point is: who does this person serve, and how well did they actually serve them?

Above expectations:

1. Built [specific relationship with a customer or stakeholder] that materially improved [specific outcome] for the team.
2. Translated [specific user feedback] into [specific change in their work] that produced measurable improvement.
3. Caught [specific stakeholder concern] early enough to address it before it escalated.
4. Set the standard for [specific kind of customer interaction] within the team, with [specific incident] as a representative example.
5. Made [specific tradeoff] explicitly in favor of long-term stakeholder trust over short-term convenience.

Meets expectations: 6. Maintained reliable communication with [specific stakeholder group] on [specific cadence]. 7. Resolved [specific kind of customer or stakeholder issue] within agreed-upon SLA. 8. Incorporated stakeholder input on [specific work] without losing sight of the team’s broader priorities. 9. Represented [specific stakeholder perspective] in [specific internal decision]. 10. Followed through on [specific commitments to stakeholders] within the cycle.

Growth needed: 11. Missed [specific stakeholder commitment] without sufficient pre-warning, requiring [specific recovery work]. 12. Showed friction with [specific kind of stakeholder] on [specific case], affecting [specific outcome]. 13. Defaulted to [specific internal lens] on [specific decision] when the situation required engaging with the stakeholder’s actual context. 14. Did not consistently follow through on [specific kind of stakeholder request] across the cycle. 15. Treated stakeholder feedback as noise rather than signal on [specific recurring topic].

5 phrases to retire from your vocabulary entirely

These show up in almost every “review phrase” list on the internet. They sound professional. They mean nothing. They will quietly damage your credibility with your direct report because they signal that you did not actually pay attention.

1. “Consistently demonstrates strong work ethic.” This describes nobody and everybody. If you mean “showed up on time” say that. If you mean “delivered hard work” name what they delivered.
2. “Is a valued member of the team.” Of course they are. They are on the team. Either name something specific they did that was valuable, or do not say it.
3. “Has room for improvement.” This is what you write when you do not want to give actual feedback. Your direct report will read it as “you have something to say but will not.” Either name the area or take it out.
4. “Exceeded all expectations.” Whose expectations? Set against what bar? If you used this phrase, you owe yourself one more sentence specifying what they exceeded.
5. “Meets the requirements of the role.” This is the corporate language equivalent of “fine, I guess.” If they actually meet the requirements, name what those requirements are and how they met them. If they barely meet them, the phrase you actually want is in section 11 of the pillar guide on common derailments.

How to take any phrase from generic to specific (the 3-step framework)

If a phrase you wrote feels generic, run it through this filter before you submit.

Step 1: Add a name. A project name, a customer name, a teammate name, a stakeholder name. Generic phrases never have names. Specific phrases always do.

Step 2: Add a number. A date, a duration, a percentage, a count, a baseline-to-actual movement. If the work has any quantitative dimension at all, surface it.

Step 3: Add the comparison. Compared to what? Last quarter? The team average? Their own commitment from the start of the cycle? Reviews that hit hardest are the ones where the reader can locate the work on a scale, not just hear that it happened.

If you cannot do all three for a sentence in your review, you have a choice. Either dig until you can, or remove the sentence. The temptation will be to leave it in because the document looks short without it. Resist. A short, specific review is more useful and more credible than a long, vague one.

Common questions

Should I quote phrases from this list verbatim?

You can, but you should always replace the bracketed items with specifics. The phrase is the structure. Your job is to fill in the structure with what actually happened. A review that reads like a phrase library will land like one.

What if my company’s HR template has its own phrase list?

Use whichever is more specific. Most HR templates trade specificity for legal defensibility, which is fine for the formal record but will not produce a useful conversation. If you are required to fill in their template, fill it in. Then write the version you actually want for the meeting and lead with that in the conversation.

How do I phrase something when the person is borderline between two ratings?

Write the evidence first, in plain language. Then look at what you wrote and see which rating it actually supports. Phrases at this point are downstream of evidence. The borderline-rating problem is almost always a borderline-evidence problem, and the answer is usually one more example, not one more phrase.

What about phrases for conversations that should become PIPs?

The phrase library above ends at “growth needed.” If you find yourself writing several “growth needed” phrases for the same person across multiple competencies, the phrase library is not the right tool. Take the Should I Put This Employee on a PIP? quiz first to check whether you are heading toward coaching or toward a formal plan. The Difficult Conversations Scripts Pack covers the conversation language you will need if a PIP becomes the right move, and the cluster article on coaching an underperformer back to meets-expectations walks through the difference between performance issues that respond to coaching and those that do not.

How do I handle promotion-relevant phrases?

If you are using the review to advocate for a promotion, you need phrases that establish “operating at the next level,” not “doing well at this level.” The Should I Promote This Employee? quiz is a useful gut check before you write, and the next-level phrases in the “above expectations” tier of each competency are the structural starting point.

My review is due tomorrow. Where do I start?

Open the pillar guide section on writing the review (section 5). It walks through the three-section structure that fits on two pages. Use this phrase library to fill in the body, not to write the whole thing. The structure is what makes the document readable. The phrases are what make it specific. You need both.

What to do this week

Pick one direct report whose review you have not yet written. Before you open the template, write down five specific things they did this cycle that you can name in detail. A project. A moment. A decision. A piece of work that surprised you, in either direction.

Now look at this phrase library. For each of the five things you wrote down, find the phrase structure that fits and fill it in.

You will have written more useful sentences in fifteen minutes than most managers produce in a full review cycle. The reason is not the phrases. It is that you started from specifics and used the phrases to dress them up, instead of starting from phrases and trying to find specifics that fit.

That is the move. Start from what you saw. Use the phrases to render it cleanly. Skip everything else.