Performance review phrases by competency give managers a ready-to-use, categorized list of comments for every key skill set, from communication to project delivery. The examples are realistic and detail-oriented, avoiding generic adjectives like “good” or “excellent.”
Use each phrase as a template, then tailor it to the employee’s specific achievements or the behavioral changes you want to encourage. This approach keeps feedback clear, actionable, and directly tied to measurable results.
For an overview of every kind of review comment, see our performance review examples.
Communication Skills
Clear, concise updates are the baseline for good communication. Look for evidence that the employee adapts tone and detail to the audience—whether it’s a quick email to a colleague or a detailed briefing for executives. Also, gauge how well they listen, ask clarifying questions, and respond promptly to follow-up queries.
Effective Communication
- “Explained the microservices architecture to the board using a simplified diagram, reducing their questions by 60% and securing approval for the migration budget within two days.”
- “Resolved a billing dispute in chat by offering a prorated credit, calming the client, and confirming satisfaction before closing the ticket.”
- “Sent a 200-word status email each Friday, highlighting milestones, blockers, and next steps, which cut the team’s weekly meeting time by 30 minutes.”
- “Demonstrated the new analytics feature to a prospect, highlighting ROI in a live demo, and secured a $45,000 order before the end of the session.”
- “Presented the updated HIPAA compliance checklist to 12 clinicians, using real-world scenarios, and achieved 100% staff sign-off within the first week.”
Communication Gaps
- “During last Friday’s 2-hour rush, staff were confused about product placement because the supervisor gave vague, spoken instructions. Provide a written checklist for rush periods and review at the next one-to-one.”
- “In the last sprint, the commit for the export feature had no description, leaving the team unclear about the change. Add a brief commit message and issue link, and verify at the end of the next sprint.”
- “The briefing email to a new retail client omitted pricing tiers, causing rework. Include standardized checklist in all briefing emails, and check compliance at next one-to-one.”
- “Minutes from last month’s meeting were 12 pages long and lacked clear action items. Limit minutes to 3 pages, start with agenda, end with actions, and review at next team meeting.”
- “A 5-day delay on the replacement fan units was not communicated until day four of the shortage. Send a delay alert within 24 hours of discovery, and confirm adherence at the next one-to-one.”
Teamwork and Collaboration
Show how much an employee shares knowledge and resources. Note their participation in group decision-making and brainstorming. Check that they reliably meet shared responsibilities.
Collaborative Contributions
- “Took on 20% of a senior designer’s workload, delivering the final mockups two days ahead of the launch deadline.”
- “Coordinated with three truck drivers to reorganize the loading sequence, reducing average dock time from 45 minutes to 30 minutes over the last two weeks.”
- “Facilitated a cross-departmental onboarding workshop that trained 25 staff in the new benefits portal, cutting initial support tickets by 40% in the first month.”
- “Shared a Power BI dashboard template that visualizes sales trends; all regional managers adopted it within two weeks, cutting report preparation time by 12 hours per month.”
- “Assisted five nurses with patient transfers during the evening shift, reducing average transfer time from 12 to 9 minutes.”
Collaboration Challenges
- “Three blockers reported last sprint were not shared, causing a 20% delay in feature delivery. Share blockers in the daily stand-up, and review adherence at the next one-to-one.”
- “Kitchen cleaning schedule remained unupdated, leading to two missed cleaning slots last month. Upload the new schedule to the shared calendar by Friday, and check compliance during the next weekly meeting.”
- “Project assistant omitted SME feedback on the Q2 proposal, resulting in a 10-day revision cycle. Incorporate SME comments before final submission, and verify completion in the next project review.”
- “Retail associate handled solo shifts efficiently but missed hand-off tasks during team shifts, causing a 15% increase in customer wait times. Create a brief hand-off checklist and complete it each shift, reviewed at the next team briefing.”
- “Accountant did not deliver the Q3 variance report by the 5th, delaying the finance closing. Submit all required data by the 3rd of each month, and confirm receipt during the next finance sync.”
Leadership and People Management
Evaluate how the employee makes decisions under pressure and the outcomes. Observe how they mentor and develop direct reports, and note the quality of coaching. Check that they set clear direction and expectations, and that those goals are achieved.
Leadership Impact
- “Led the merger integration, aligning 12 cross-functional teams and completing the transition plan two weeks ahead of the target deadline, resulting in a 95% retention of key talent.”
- “Coached the new hire through the launch of the client-feedback portal, culminating in a 30-ticket sprint that met the release date and exceeded quality benchmarks.”
- “Took charge of the system outage, coordinated real-time diagnostics across three data centers, and restored full service within 2.5 hours, limiting customer impact.”
- “Implemented a daily incentive leaderboard, boosting holiday sales by 18% month-over-month and achieving the highest single-day revenue in the store’s history.”
- “Orchestrated a team of 15 freelancers across three continents, establishing clear milestones in Asana, and delivered the new e-commerce platform on schedule with zero scope creep.”
Leadership Development
- “Delegation attempts limited to one senior member, causing a 30% delay in task turnaround. Assign at least one non-critical task to a junior each sprint, review progress at the next one-to-one.”
- “One-to-ones lacked specific performance metrics; two team members reported unclear expectations. Include a quarterly goal review in each session, evaluate effectiveness at the next one-to-one.”
- “Directions for data entry differed between two analysts, leading to duplicated effort. Create a shared SOP and train both analysts by end of Q2; compliance verified in next team meeting.”
- “Scope change for the client portal rollout was not communicated to stakeholders until the last week, causing a 2-day delay. Draft a change-notification email within 24 hours of any scope update, check adherence at the next sprint review.”
- “Conflict between two shift members escalated, impacting morale. Intervene by mediating a 15-minute discussion within 30 minutes of the first sign of tension, review resolution at the next shift briefing.”
Time Management
Use these phrases to judge how well an employee estimates task duration, manages competing priorities, and sticks to project timelines. Adjust the wording to fit the specific role and the level of detail required for each competency.
Efficient Workflow
- “Managed three executive calendars, scheduling 120 appointments per month with zero conflicts and a 100% on-time meeting rate.”
- “Delivered 12 feature articles each month, 2–3 weeks ahead of the editorial calendar, enabling the team to publish on schedule.”
- “Redesigned delivery routes, cutting average transit time from 3.5 to 2.8 hours and keeping on-time deliveries at 99%.”
- “Resolved 350 support tickets weekly, closing 95 out of 100 on first contact and keeping CSAT above 4.5/5.”
- “Completed every sprint commitment for three consecutive cycles, delivering 18 user stories on time and with zero defect rework.”
Prioritization Needs
- “Spending over two hours on each invoice detail caused the Q2 financial report to be submitted three days late; streamline detail review by setting a 15-minute cap per invoice and we’ll check progress at the next one-to-one.”
- “Balancing restocking 200 units weekly with customer assistance led to a 20% rise in checkout wait times; prioritize stock tasks by allocating 30 minutes each shift before opening and review impact in 30 days.”
- “Three campaign launch dates slipped because the initial timeline omitted a two-week creative review; incorporate a mandatory review checkpoint in all future briefs and we’ll assess adherence at the next quarterly review.”
- “Daily task list remained untracked, causing missed deadlines; implement a shared task board and update it before each stand-up, with progress reviewed at the next one-to-one.”
Problem Solving
These phrases help you gauge analytical thinking and data use, spot root causes instead of symptoms, and reward creative problem-solving. Use them to ask for specific examples, ask how decisions were backed by data, and highlight innovative solutions that overcame obstacles. Adjust wording to fit the employee’s role and the context of the issue.
Analytical Problem Solving
- “Identified a recurring memory leak in the legacy CRM module, wrote a patch that reduced crash rates by 27% over two release cycles, and documented the fix in the internal knowledge base.”
- “Redesigned the assembly line layout to eliminate two redundant conveyor steps, cutting material waste by 15% and shortening cycle time by 3 minutes per unit in the first month of implementation.”
- “Detected a $4,500 over-allocation in the Q2 marketing budget during a variance review, corrected the entry before the audit, and prevented a potential $12,000 overrun.”
- “Resolved a multi-year billing dispute for a key client by reconciling 112 invoices, issuing a credit memorandum, and restoring the account balance within 10 business days.”
- “Implemented modular repair kit for HVAC units, cutting repair labor hours by four each month and saving $8,000 annually versus outsourced services.”
Problem Solving Gaps
- “Applied the same temporary fix to the recurring login error 12 times this quarter, keeping tickets open longer. Document root causes in each ticket before closing, and review compliance at the next one-to-one.”
- “Missed key supplier delay risks in the Q2 rollout, causing a 3-day backlog. Map critical dependencies in the project plan now, and verify risk coverage at the next project review.”
- “Struggled to source a replacement for the out-of-stock widget, delaying the client demo. Build a backup supplier list by end of month and confirm stock with alternate suppliers before the next pitch.”
- “Requested help on basic code syntax 15 times this period without prior research. Complete the internal coding guide by next week and attempt troubleshooting before reaching out, and we’ll evaluate progress at the next one-to-one.”
- “Failed to resolve the vendor delivery delay for the office supply order, leaving the team short three days. Search for alternative vendors in the database now, and check the new solution at the next inventory meeting.”
Adaptability
Evaluate how quickly the employee adopts new tools and processes. Observe their resilience during organizational change, noting how they maintain performance. Measure the speed at which they learn new job requirements and adapt to shifting priorities.
Adaptability Strengths
- “Mastered the new CRM within two weeks of rollout, completed 95% of data migration tasks ahead of schedule and trained three teammates on advanced features.”
- “Pivoted the data migration project to focus on customer segmentation after the strategy shift, delivering the new dashboard 10 days early and increasing reporting accuracy by 18%.”
- “Transitioned from in-store packing to online fulfillment, processing 120 orders daily and reducing packaging time by 25 minutes per batch.”
- “Adopted the new micro-services framework within two days, refactored three legacy modules, and cut build times from 12 to 8 minutes.”
- “Led the team through the remote-work policy change, introduced a new collaboration protocol, and kept project completion at 49 of 50 tasks during the transition.”
Adaptability Challenges
- “Three months into the new digital filing system, only 45% of files were migrated, causing duplicate work. Switch to the new system for all new files, and verify 90% migration by next one-to-one.”
- “When the daily stand-up moved to 10 am, output dropped 20% and missed two client deadlines. Implement a brief pre-stand-up prep routine, and review productivity metrics in 30 days.”
- “Since the new org chart, team leads are unclear on reporting lines, leading to duplicated effort. Attend the upcoming leadership workshop and map reporting paths by end of next week.”
- “Project scope changed every two weeks, causing task completion to lag by 3 tasks this quarter. Adopt a change-log template and review its effectiveness at the next one-to-one.”
- “New reporting template has delayed the analyst’s turnaround by 3 days each week. Complete the template training module and submit the next report using the new format by the end of next week.”
Competency-Based Review Templates
Use the Action + Context + Result formula to craft each comment.
Each example below shows how to state what was done, where it happened, and the impact.
Add a clear next step so the employee knows exactly how to improve.
Positive Achievement Template
Use this when you want to highlight a specific competency that led to a measurable outcome and outline the next development step.
{Employee name} consistently demonstrates strong {competency} by {specific action}, resulting in {result with number} improvement. The next step is {next step}. Review scheduled for {review date}.
Filled-in examples:
- “Led the migration of the legacy ticketing system to ServiceNow, completing the project 3 weeks ahead of schedule and reducing ticket resolution time by 18%.”
- “Consistently demonstrates meticulous data validation, cutting quarterly report errors from 4 per 100 to 0.5 per 100 and saving the audit team 5 hours monthly.”
- “Successfully managed the cross-department rollout of the new compliance dashboard, achieving full user adoption within 6 weeks and eliminating manual data pulls.”
Constructive Growth Template
Use this when you want to give concise, constructive feedback on a specific competency, such as teamwork, communication, or problem-solving, and outline a clear next step.
{employee name} consistently demonstrates strong {competency} by {specific example}. To build on this, {next step} will help {desired outcome}. We'll review progress on {review date}.
Filled-in examples:
- “Observed tendency to include excessive detail in client status emails, delaying decision making and causing two project approvals to slip past the deadline. To improve, start each email with a concise summary and deadline, then add supporting data; review progress at the next weekly sync in Q3.”
- “Struggles with generating weekly performance dashboards, leading to a 15% increase in manual data entry errors. Aim to complete the dashboard template by next Friday and schedule a brief training session with the analytics team.”
Write from the employee’s perspective, not yours. Use “the employee” or “they” and focus on observable actions. For example: “The employee consistently meets deadlines and delivers high-quality reports.” Avoid “I” and keep the tone objective.
What is the difference between a competency and a soft skill in a review?
A competency is a specific, job-related skill or behavior that can be measured and tied to performance outcomes, while a soft skill is a general personal trait that supports effective interaction but isn’t always directly linked to job tasks. For example, “Demonstrates strong analytical competency by accurately forecasting quarterly sales” shows a competency; “Shows empathy when handling customer complaints” reflects a soft skill.
Include about 3–5 phrases per competency. That gives enough depth without overwhelming the review. For example, for “Collaboration” you might write: “Consistently shares insights and supports teammates, leading to smoother project delivery.” This keeps the feedback focused and actionable.
How can I make constructive feedback feel less personal?
Make feedback objective and action-oriented. Focus on specific behaviors, not the person. Use “I” statements that describe the situation and the impact, then suggest a next step. For example: “When the report was submitted late, the team missed the deadline. Let’s set a weekly check-in to keep on track.” This keeps the comment factual and constructive.
These examples show structure and wording only. They are not HR or legal advice. Every name and scenario is fictional; adapt each comment to the employee’s actual work and evidence, and follow your organization’s review policies.
Write every review without starting from scratch
Save the review comments you reuse to TextOps and insert them into any HR system or document, so every review cycle starts from wording you trust.
Install TextOps