I’ve reviewed a lot of performance review guides. Most of them hand you a list of phrases and leave you to figure out the rest. What they rarely tell you is why those phrases work, or how to adapt them when the situation is messier than the template assumes.
This guide does things differently. You’ll get 100 performance review examples and phrases, but also the context to use them well: what makes feedback land, which phrases to stop using immediately, and how to match your language to the type of review you’re running.
Use this as a working reference, not a script. Every phrase here is a starting point. The best performance review examples are the ones you adapt to a real person in a real situation.
A useful review phrase is specific, behavior-based, and forward-looking. If the employee can’t picture a real moment it refers to, the phrase won’t drive any change.
Most performance review feedback fails for one of three reasons: it’s too vague to be actionable, it focuses on personality instead of behavior, or it stops at the observation without pointing somewhere useful.
Before you start writing, run each phrase through this quick filter:
One framework worth keeping in mind is SBI: Situation — Behavior — Impact.
You don’t need to use it rigidly, but it gives your feedback a clear structure. “During the Q3 product launch [Situation], you took ownership of coordinating across three teams without being asked [Behavior], which meant we shipped on time despite the resourcing constraints [Impact].” That’s the kind of feedback that actually sticks.
Vague phrases waste everyone’s time. If you can’t tell which employee the comment is about, rewrite it.
Here are the most common performance review phrases that sound useful but aren’t, paired with sharper rewrites you can use instead.
| Weak phrase | Why it fails | Better version |
|---|---|---|
| Great team player | Tells the employee nothing specific | Consistently supports teammates under pressure; stepped in to cover X’s scope during the Q3 deadline without being asked |
| Needs to improve communication | No indication of what ‘better’ looks like | Updates stakeholders reactively, rather than proactively; aims to send a project status note before questions come in |
| Always meets deadlines | Too absolute; ‘always’ is rarely true | Has met every agreed deadline this half, including two that required significant overtime in the final week |
| Shows great leadership | Leadership is not a behavior | Ran weekly team standups in the manager’s absence, keeping the team aligned without escalating to leadership once |
| Could show more initiative | No direction; initiative on what, exactly? | Has strong execution skills; the next step is identifying process improvements independently, not waiting to be assigned them |
| Good attitude | Personality, not performance | Approaches difficult client situations with patience and professionalism, which has protected several key relationships this year |
| Needs to be more strategic | Unclear without context | Currently focused on task-level execution; development focus for the next half is contributing to quarterly planning conversations |
| Works well under pressure | Vague and unverifiable | During the system outage in March, diagnosed the issue and coordinated the fix within four hours, keeping the team calm throughout |
| Room for improvement | Tells them nothing | Response time on support tickets averaged 36 hours last quarter — the target is 24. A weekly prioritization check-in would help close that gap |
| A valuable member of the team | Generic closing filler | Her client retention rate of 94% this year has directly contributed to hitting our Q4 revenue target |
Organized by ten core competencies. Each phrase is followed by a development action, one concrete next step that turns the feedback into a plan.
I’ve split each category into positive feedback and areas for development. Use the development actions as a prompt for the follow-up conversation, not a directive to paste into the form.
Positive examples
| Strength | Evidence | Development Action |
| Clear written communication | Project updates require almost no editing before reaching leadership. | Mentor a junior team member on written communication. |
| Audience-aware communication | Technical details go to engineers; outcome summaries go to executives. | Co-present at the next QBR. |
| Constructive feedback delivery | Gives direct feedback that remains well-received during difficult conversations. | Take a larger role in retrospectives. |
| Proactive stakeholder communication | No stakeholders were surprised by deadlines or blockers. | Document the communication process for team reuse. |
| Cross-functional facilitation | Led three productive workshops this quarter. | Lead the next department all-hands. |
Needs development
| Development Area | Evidence | Development Action |
| Proactive stakeholder communication | Updates tend to come reactively, after stakeholders have already asked. | Set a recurring task to send project status notes every Friday by noon. |
| Executive-style writing | Written reports are detailed but difficult to scan, with key decisions buried in the middle. | Practice leading with the conclusion and attend the internal writing workshop in Q2. |
| Leadership presentation confidence | Comfortable presenting to peers but less confident in leadership forums. | Take one lightning talk slot at the monthly team meeting. |
| Written feedback clarity | Written feedback often requires follow-up clarification from recipients. | Write a one-paragraph summary after each one-to-one feedback conversation. |
| Meeting facilitation balance | Occasionally dominates team discussions, limiting input from quieter team members. | Experiment with structured round-table formats in meetings led. |
Positive examples
| Strength | Evidence | Development Action |
| Consistent delivery quality | Deliverables are consistently accurate and complete, with no work requiring rework this year. | Share the QA process with the wider team as a repeatable template. |
| Attention to detail | Caught three significant data errors in the quarterly report before board submission. | Create a formal pre-submission checklist for team use. |
| Strategic thinking | Produces work that exceeds the brief without creating scope creep by anticipating stakeholder needs. | Apply this foresight more directly to product roadmap planning. |
| Reliability under delivery standards | Has not missed a quality threshold across twelve projects delivered this half. | Take on higher-complexity projects requiring more independent judgment. |
| First-draft quality | Consistently delivers client-ready output on the first draft, reducing rework time across projects. | Lead a peer review process to help raise overall team standards. |
Needs development
| Development Area | Evidence | Development Action |
| Accuracy and self-review | Work is generally directionally correct but often requires editing for accuracy before sharing. | Build in a mandatory personal review step before submission. |
| Balancing speed and quality | Work is delivered quickly, but quality drops under tight timelines. | Align with the manager on which deadlines are flexible so that revision time can be protected. |
| Quality assurance consistency | Errors in client deliverables were flagged twice this quarter. | Partner with a senior team member for QA reviews on the next three projects. |
| Handling ambiguity | Output quality is strong with clear briefs but weaker when requirements are unclear. | Use a standard set of scoping questions before beginning work. |
| Depth of critical thinking | Work consistently meets the baseline standard but rarely goes beyond it. | Before submitting, identify one improvement that would materially strengthen the output. |
Positive examples
| Strength | Evidence | Development Action |
| Psychological safety and trust | Creates an environment where team members feel comfortable raising problems early, preventing issues from escalating. | Share this approach with newer team leads. |
| Team-first mindset | Volunteered to support two additional teams during the product launch without being asked. | Help design a formal mutual-support process for the team. |
| High-value peer feedback | Provides honest and actionable peer review feedback that teammates consistently find useful. | Participate in the performance calibration process. |
| Conflict resolution | Resolves interpersonal friction quickly and fairly without management escalation. | Mentor a junior team member on conflict resolution techniques. |
| Cross-functional collaboration | Consistently involves the right stakeholders at the right time, improving project flow. | Document the stakeholder-management approach for future project leads. |
Needs development
| Development Area | Evidence | Development Action |
| Collaborative communication | Tends to work independently on tasks that require more collaboration, leaving teammates under-informed. | Establish a regular check-in rhythm with key collaborators at the start of projects. |
| Constructive peer feedback | Peer review feedback is supportive but often lacks actionable value for the recipient. | Use the SBI framework with one clear strength and one development point per review. |
| Conflict management | Ongoing conflict with a teammate is beginning to affect the wider team dynamic. | Schedule a facilitated conversation with HR support before the end of the month. |
| Workload transparency | Protectiveness over workload ownership has created bottlenecks for others. | Use a shared task board to improve visibility and reduce gatekeeping. |
| Initiative beyond role scope | Participates well within defined responsibilities but contributes less outside them. | Identify one area this quarter to contribute beyond the formal role scope. |
Positive examples
| Strength | Evidence | Development Action |
| Deadline reliability | Has met every agreed deadline this year, including projects where the scope expanded mid-delivery. | Take ownership of a project with full end-to-end timeline management. |
| Proactive risk management | Consistently identifies timeline risks early enough for the team to adjust. | Create a reusable risk-flagging template for the wider team. |
| Workload management | Handles a high volume of concurrent tasks without a visible decline in quality. | Share the prioritization system in a team knowledge session. |
| Accurate project estimation | Estimates timelines realistically and rarely requires extensions. | Participate in roadmap scoping discussions next quarter. |
| Professional reliability | Maintains a dependable meeting presence, with cancellations communicated early and infrequently. | Take on a recurring facilitation role in the weekly team sync. |
Needs development
| Development Area | Evidence | Development Action |
| Deadline consistency | Missed three internal deadlines this quarter, all tied to report submissions. | Identify whether the root issue is estimation, prioritization, or workload, and align with the manager on a solution this week. |
| Commitment management | Regularly accepts commitments faster than delivery capacity allows. | Review current workload before accepting additional requests and negotiate timelines where needed. |
| Prioritisation | Lower-priority tasks sometimes receive disproportionate attention over higher-impact work. | Set up a weekly prioritization review with the manager until the pattern improves. |
| Professional punctuality | Attendance times for client meetings have been inconsistent. | Build in a mandatory five-minute buffer before all client calls. |
| Long-project planning | Planning discipline tends to weaken during the final stages of longer projects. | Introduce a structured mid-project review two weeks before deadlines to surface risks earlier. |
Positive examples
| Strength | Evidence | Development Action |
| Process improvement initiative | Identified a long-standing workflow inefficiency and built a solution within two days, saving an estimated four hours per week. | Present the initiative at the next all-hands meeting. |
| Crisis management and adaptability | Secured and onboarded a replacement vendor two weeks before launch without delaying delivery. | Document the vendor contingency process for future projects. |
| Structured problem-solving | Consistently approaches problems through data gathering and option evaluation, leading to well-supported decisions. | Lead the next cross-functional problem-solving session. |
| Risk anticipation | Flagged three major risks in the past six months that could have caused significant delays. | Contribute to the risk register process during the next product cycle. |
| Independent decision-making | Keeps workstreams moving in ambiguous situations without waiting for direction. | Maintain a visible decision log for key judgment calls. |
Needs development
| Development Area | Evidence | Development Action |
| Independent problem-solving | Tends to escalate blockers before attempting to solve them independently. | Spend 20 minutes testing possible solutions before escalating, and document what was tried. |
| Systems thinking | Solutions are usually correct, but do not always account for downstream impact on other teams. | Review proposed solutions with at least one stakeholder outside the immediate team. |
| Proactive risk recognition | Responds well to problems once they occur, but has not consistently demonstrated anticipation of recurring issues. | Attend the next sprint retrospective to identify recurring failure patterns. |
| Strategic problem framing | Performs strongly within defined scopes but struggles when problems require reframing. | Explore design thinking or root cause analysis methods to expand the problem-solving approach. |
| Problem definition discipline | Moves to execution quickly without always fully understanding the underlying issue. | Write a short problem statement before proposing or implementing solutions. |
Positive examples
| Strength | Evidence | Development Action |
| Psychological safety leadership | Built a team culture where people feel safe raising concerns, contributing to an 18-point increase in psychological safety scores this year. | Share the team norms document with other team leads. |
| Clear delegation and autonomy | Creates clarity around decision ownership so team members know when to act independently and when to escalate. | Document the delegation framework for new managers. |
| Change leadership | Managed two restructuring conversations with transparency and care, maintaining steady engagement throughout. | Contribute this experience to the next manager training cohort as a case study. |
| Coaching capability | Uses one-to-ones to coach team members toward stronger independent thinking and capability. | Formalize the coaching approach into a reusable manager template. |
| Talent development | Developed two direct reports for promotion readiness within the past year. | Take on a stretch assignment leading a cross-functional team. |
Needs development
| Development Area | Evidence | Development Action |
| Coaching effectiveness | Strong technical capability has not yet translated into equally strong team coaching. | Shadow a senior manager’s one-to-one sessions monthly and debrief afterwards. |
| Inclusive decision-making | Team decisions are sometimes made without enough input from the people affected by them. | Run a retrospective focused on where broader involvement was needed. |
| Feedback consistency | Feedback is delivered infrequently, allowing issues to build before being addressed. | Provide at least one specific piece of feedback to each direct report every week. |
| Leadership visibility | Leadership influence remains largely limited to the direct team. | Sponsor or champion one cross-functional initiative in the next half. |
| Performance management structure | Individual performance conversations are handled inconsistently and not always documented formally. | Use a standard template for all formal feedback conversations starting next quarter. |
Positive examples
| Strength | Evidence | Development Action |
| Applying feedback effectively | Feedback discussed in January is now clearly reflected in day-to-day work and behavior. | Begin actively gathering feedback from peers in addition to managers. |
| Self-directed learning | Proactively pursued three formal learning opportunities this year without prompting. | Share key learnings with the team through a short knowledge-sharing session. |
| Growth mindset | Responds to critical feedback constructively and demonstrates clear follow-through on areas for improvement. | Take on a stretch project outside the current comfort zone. |
| Technical development | Expanded from a support-level contributor to an independent contributor on the platform team. | Set a goal for the next technical certification to pursue. |
| Proactive development planning | Uses one-to-ones to identify growth opportunities before they become formal requirements. | Build a six-month development plan with clear milestones and checkpoints. |
Needs development
| Development Area | Evidence | Development Action |
| Feedback receptiveness | Tends to resist feedback initially before later acting on it. | When receiving difficult feedback, identify and write down one element that may be valid before responding. |
| Growth momentum | Skill development has plateaued relative to expectations at this level. | Set a specific learning objective for next quarter with a measurable outcome. |
| Translating feedback into change | Similar feedback has appeared across multiple review cycles without visible behavioral change. | Focus on one concrete behavior change and review progress after 30 days. |
| Comfort with ambiguity | Discomfort with undefined problems is limiting progression into more senior-level work. | Take ownership of one ambiguous task per sprint and document the decision-making process. |
| Career ownership | Demonstrates capability for the next level but has not yet shown sustained initiative toward it. | Hold a direct career planning conversation with the manager and define a progression plan. |
Positive examples
| Strength | Evidence | Development Action |
| Goal execution | Achieved all four quarterly targets, including one that required a major mid-cycle adjustment in approach. | Take ownership of setting next quarter’s goals with minimal guidance. |
| High-performance delivery | Exceeded sales targets by 23% while maintaining client satisfaction above 90. | Document the drivers behind the performance and share them with the wider team. |
| Transparent goal management | Delivered on commitments and raised risks early when one goal became unachievable, allowing reprioritization without disruption. | Apply the same transparency to a team-level initiative. |
| Strategic goal-setting | Consistently sets ambitious but achievable goals, building strong credibility with senior stakeholders. | Contribute more actively to team-level goal-setting discussions. |
| Stretch performance | Achieved a stretch goal reached by fewer than 20% of peers this cycle. | Define the next stretch objective aligned with progression to the next level. |
Needs development
| Development Area | Evidence | Development Action |
| Goal attainment consistency | Two of four quarterly goals were missed, both tied to client delivery outcomes. | Complete a root-cause analysis this week and align with the manager on a revised approach before the next cycle. |
| Ambition in goal-setting | Goals are often set conservatively, limiting growth potential and broader contribution. | Include at least one goal next quarter that feels meaningfully challenging. |
| Progress monitoring | Goal tracking has been inconsistent, reducing opportunities for mid-cycle correction. | Schedule fortnightly goal reviews and proactively share progress updates. |
| Strategic ambition | Execution is reliable, but current goals do not reflect the ambition expected at this level. | Align with the manager on what high performance looks like at the next level and build goals backward from that standard. |
| Quality alignment in goals | Output targets were achieved, but quality expectations were not met and were not reflected in the goal structure. | Redesign goals to include both output and quality metrics. |
Positive examples
| Strength | Evidence | Development Action |
| Adaptability during change | Reworked the project plan within 48 hours after a major strategy shift in week six, keeping delivery on track. | Lead the next team change-management communication. |
| Rapid learning capability | Took on an entirely new functional area mid-year and reached senior-level output within six weeks. | Document the learning approach so others can replicate it. |
| Stability under pressure | Manages competing priorities calmly, helping maintain team stability during high-pressure periods. | Share the prioritization framework during the next team retrospective. |
| Strategic and operational flexibility | Shifts effectively between strategic thinking and detailed execution based on situational needs. | Take on a role requiring both strategic and execution ownership over a sustained period. |
| Positive response to change | Navigated four major process changes this year while maintaining a consistently constructive attitude. | Act as a change champion during the next system migration. |
Needs development
| Development Area | Evidence | Development Action |
| Openness to change | Established process changes are often met with resistance, slowing team adaptability. | During the next major change, deliberately identify one potential positive outcome before raising concerns. |
| Adaptability under shifting priorities | Performance declines when priorities change rapidly or unpredictably. | Track and compare top priorities at the start and end of each day to strengthen reprioritization habits. |
| Comfort with ambiguity | Ambiguity creates hesitation that limits independent action. | Take ownership of one undefined task each week without immediately seeking clarification. |
| Adapting to collaborative working models | Has struggled to adjust working style to fit a more collaborative team structure. | Identify one outdated working habit to stop and one collaborative behavior to strengthen. |
| Resilience after setbacks | Recovery from setbacks takes longer than expected for this level. | After the next setback, document lessons learned within 24 hours to accelerate recovery and reflection. |
Positive examples
| Strength | Evidence | Development Action |
| Exceptional overall performance | Delivered high-quality work, contributed strongly to the team, and consistently achieved every goal this year. | Define a clear progression path to the next level with measurable H1 milestones. |
| Sustained high performance | Has exceeded expectations consistently across two review cycles, demonstrating durable high performance rather than a short-term peak. | Explore potential leadership-track opportunities. |
| Resilience and consistency | Maintained strong performance through significant personal and organisational challenges. | Identify the highest-priority growth area for the coming year. |
| Trust and influence | Has become one of the most trusted people on the team, with peers and senior stakeholders actively seeking involvement and input. | Take on a cross-functional leadership opportunity in the next cycle. |
| Initiative beyond expectations | Delivered all assigned responsibilities while independently identifying and completing additional high-value work. | Formalise ownership by leading a defined workstream. |
Needs development
| Development Area | Evidence | Development Action |
| Performance consistency | Performance fell below expectations in two of the four key areas this cycle. | Create a 60-day improvement plan with defined milestones and a 30-day review checkpoint. |
| Consistency of output | Demonstrates the capability for higher-level performance, but delivery has been inconsistent this cycle. | Identify the primary factors affecting consistency and address those first. |
| Handling ambiguity | Execution is strong on established work but weaker when challenges are new or undefined. | Take ownership of one ambiguous project in H1 with structured manager support. |
| Readiness for progression | Meets current expectations but has not yet demonstrated readiness for the next level. | Define the expectations of the next level clearly and build a development plan backward from them. |
| Team-level impact | Individual contribution is strong, but broader influence on team outcomes remains limited. | Set at least one goal next cycle focused on enabling or influencing others. |
The review format changes what you’re trying to achieve, and the language should follow. Annual reviews call for summative language; peer reviews require a different tone; self-assessments need to avoid both underselling and over-inflating.
Annual reviews carry more weight, so the language should be more considered. Focus on patterns across the full year, not individual incidents. Use evidence-based framing and tie the summary to what happens next.
Peer and 360° reviews should be honest but constructive. Your job is not to be your colleague’s biggest fan or their harshest critic. Focus on what you’ve directly observed working alongside them.
Writing about yourself is hard. Most people either undersell to appear humble or overstate to manage impressions. Neither is useful. The goal is an honest account of where you delivered value and where you know you fell short.
Check-in language should be lighter and more forward-looking than an annual review. Less verdict, more direction.
Hard feedback is most useful when it’s specific, delivered without judgment, and paired with a clear path forward. Vague concern: “I’m worried about your performance” gives the person nothing to work with
Here are performance review examples for the situations most managers find hardest to put into words.
PIP language needs to be clear, specific, and fair. It should document the situation accurately and give the employee a genuine path to success, not just create a paper trail.
Check out our Performance Improvement Plan Template: Free Download + Complete Guide
A performance review example that ends with the feedback is only half-finished. The other half is what happens next.
Every piece of review feedback, positive or developmental, should lead somewhere. If it doesn’t, you’re documenting the past without shaping the future.
Here’s a simple structure that works:
| Step | What it looks like |
|---|---|
| The phrase | Consistently updates stakeholders reactively rather than proactively |
| The goal | By the end of Q2, all project stakeholders will receive a status update before they need to ask for one |
| The 90-day milestone | In the next sprint, send at least two unprompted status notes to key stakeholders and share the responses with your manager |
| The check-in | We’ll review this at your next monthly one-to-one |
When your reviews are tied to structured goals like this, they become part of a continuous cycle rather than a once-a-year event. That’s where performance conversations start to actually move things.
If you’re running performance reviews on a spreadsheet or through email, Thrivea’s performance management module gives you goal-setting, review cycles, and 360° feedback in one place, so the conversation you have in the review connects directly to the goals you track throughout the year. It’s free to get started.
Check out our guide How to Choose Performance Review Software
The best performance review examples share three things: they describe a specific behavior, they note its impact, and they point to something useful. Everything else, the exact wording, the competency category, the review format, is secondary to those three things.
Use this guide as a toolkit, not a script. The phrases here are starting points. The version that lands in your review is the one you adapt to the person in front of you.
And if you want the feedback you give to connect directly to goals your team tracks through the year, that’s exactly what Thrivea is built to do.
How do I write a performance review for someone who exceeds expectations?
Focus on specific outcomes and the impact beyond their role: what did they do that nobody asked them to, and how did it affect the team or business? Then use the review to map out what the next level looks like and make that conversation explicit.
What should I write in a performance review for a new employee?
Anchor it in what they were expected to achieve in their first 90 to 180 days, not against the full job spec. Focus on learning pace, integration into the team, and early indicators of their approach to their work. Avoid comparing them to longer-tenured peers.
How do you write constructive feedback without sounding harsh?
Lead with specificity, not softening. Vague reassurance followed by a criticism (“you’re great, but…”) reads as insincere. Instead, name the specific situation, describe the behavior, explain the impact, and then offer a concrete path forward. That structure feels fair because it is.
What are good phrases for a self-performance review?
Be specific about what you delivered and what evidence supports it. Name your development area honestly; managers notice when it’s clearly sanitized. Close with what you want to focus on next and why, rather than asking what the company will do for you.
How many phrases should a performance review have?
There’s no ideal number, but depth beats volume. One well-written, specific phrase per competency area is worth more than five generic ones. For an annual review, aim for 3–5 substantive observations per person, each with a development action, rather than a long list of one-liners.
by Jelena Relić
Most companies have HR managers. Fewer have an HRBP, and the difference matters more than most people realize. An HR Business Partner (HRBP) isn't jus...
by Jelena Relić
Most managers walk into a one-on-one meeting with no plan and walk out wondering why it felt like a status update. The right one-on-one meeting questi...
by Jelena Relić
20 areas of improvement at work examples for performance reviews, organized by skill category, with a step-by-step process for turning feedback into d...
Feel free to send us your questions or
request a free consultation.
© 2026 — THRIVEA. All rights reserved.
Also from our team
The engagement side of modern people ops
