Performance review examples and phrases that actually work

Writing effective performance review comments is harder than it looks. Generic praise ("great team player," "excellent communicator") is meaningless and legally weak. Generic criticism without behavioral evidence creates conflict and invites pushback. The best performance review comments are specific, behaviorally anchored, and connected to the expectations of the employee's career level.

This article provides real examples organized by competency area and performance level — examples you can use as a starting point and adapt to your specific context.

The structure of a useful performance review comment

Every effective review comment contains three elements:

1. Observation. What did the person specifically do or say? Reference real situations, not impressions. "Led the Q3 roadmap prioritization process" not "showed leadership."
2. Impact. What was the outcome? Why does it matter? "Resulting in the team shipping two features that reduced support ticket volume by 30%."
3. Context. What level is this relative to expectations? "This is the kind of ownership we expect at L5 — something that marks a clear shift from the previous review period."

Communication — review examples by performance level

Exceeding expectations:

• "Consistently sets the standard for written communication on the team. The Q2 engineering RFC she wrote was so well-structured that it became the template for all subsequent RFCs. Stakeholders from three teams cited it as the clearest technical proposal they had reviewed all year."
• "Has developed a remarkable ability to translate technical complexity for non-technical audiences. His explanation of the new data pipeline architecture at the all-hands removed what had been a persistent source of confusion among the product and sales teams."

Meeting expectations:

• "Communicates project status clearly and proactively. Weekly updates to stakeholders are timely and include appropriate context on blockers. Has grown in her ability to raise issues early rather than waiting until they become critical."
• "Written documentation is clear and organized. Could continue to develop the skill of adapting communication style for different audiences — technical accuracy is strong; the next step is calibrating depth for non-engineers."

Below expectations:

• "Three project delays in Q2 and Q3 were preceded by insufficient stakeholder communication. In each case, risks that were known internally were not escalated in time for stakeholders to adjust. This is the most important development area for the next period."
• "Written proposals often lack the context stakeholders need to make decisions without follow-up conversations. The goal for H2 is to write proposals that stand alone — one proxy: fewer clarification emails after the document is shared."

Execution and delivery — review examples by performance level

Exceeding expectations:

• "Delivered the payments integration project on schedule despite two significant scope changes mid-execution. Rather than treating the changes as blockers, she re-planned the work within 48 hours and kept the timeline intact. This is exactly the kind of adaptability we need at this level."
• "Has not missed a commitment this year. More importantly, the quality of output has been consistently high — not just hitting deadlines but delivering work that requires minimal rework."

Meeting expectations:

• "Generally reliable on delivery. Occasionally takes on more than is achievable in the sprint and has been working on being more conservative in initial estimates. Has improved noticeably in Q4 — estimates are more accurate and exceptions are flagged earlier."
• "Delivers individual projects on schedule. The development area is scope management — keeping a project on track when requirements shift mid-execution is the next level of execution skill to develop."

Below expectations:

• "Five of eight Q2 deliverables were late, with two requiring escalation. The pattern is consistent: tasks are started on time but scope and complexity are underestimated, and delays are not surfaced until the deadline has passed. We have discussed this directly; the next review period is the window to demonstrate improvement."

Collaboration and teamwork — review examples

Exceeding expectations:

• "Has become a connective tissue for the cross-functional pod. She proactively surfaces blockers that other team members have not raised, brokers alignment between engineering and product on ambiguous requirements, and consistently models the kind of collaborative behavior that makes the team faster."
• "His willingness to unblock teammates — even at the cost of his own project velocity in the short term — has had measurable impact on the team's overall throughput. Three engineers have specifically cited him as someone who made them more effective."

Meeting expectations:

• "Works well with teammates on shared projects. Participates constructively in team discussions and does not create friction in cross-functional work. The development area is becoming more proactive in identifying how his work intersects with others' before being asked."

Below expectations:

• "Feedback from two peer reviews noted that she tends to work in isolation on tasks that require coordination. Two projects in H1 had integration problems that could have been avoided with earlier cross-functional communication. This is a pattern worth addressing directly in the IDP."

Leadership and influence — review examples

Exceeding expectations:

• "Has moved from executing within defined scope to actively shaping scope. The decision to refactor the authentication service — a proposal he drove from identification through executive alignment — saved an estimated 200 engineering hours over the following quarter."
• "Mentored two junior engineers this year, both of whom have meaningfully accelerated their development. Her investment in others is visible in their output quality, not just their appreciation."

Meeting expectations:

• "Shows appropriate judgment in decision-making within her scope. Beginning to take on more informal mentorship of newer team members. The next level is owning the narrative for significant technical decisions — bringing recommendations fully formed to stakeholders rather than waiting to be asked."

Below expectations:

• "At L4, we expect independent ownership of projects, including stakeholder alignment. In the last two cycles, both projects required significant manager involvement in stakeholder conversations that should have been led independently. This is the most important gap to close for a promotion discussion."

Goal achievement — review examples

Exceeding expectations:

• "Achieved all three OKR key results for Q3, with KR2 (reduce API p99 latency from 800ms to 400ms) exceeded at 320ms. More impressively, she identified a fourth opportunity that was not in the original OKR and drove it to completion, reducing infrastructure cost by 15%."

Meeting expectations:

• "Hit two of three key results for the half. KR3 (implement automated regression suite) was partially completed at 65% — the remaining work is scoped for Q1. Overall, a solid performance against goals with one item carrying over."

Below expectations:

• "Two of three Q3 goals were not completed. The pattern was not a lack of effort but consistent underestimation of complexity at the planning stage. For H2, the development goal is to improve estimation accuracy — the target is 80% of goals completed within the original timeline."

What to avoid in performance reviews

• Vague superlatives: "Absolutely outstanding," "truly exceptional," "a genuine pleasure" — these feel good but say nothing useful and cannot support a compensation or promotion decision.
• Personality judgments: "Has a great attitude," "is not a team player" — these describe character, not behavior. They invite dispute and have no legal standing. Describe observable actions instead.
• Recency bias: Reviewing only the last 60 days of a 6-month period. Address this by pulling goal documentation, project notes, and peer feedback from the full period before writing.
• Burying critical feedback: A critical development need mentioned briefly at the end of an otherwise positive review will not be heard. If something matters, it needs dedicated space and clear language.

For the full review process, see How to Run a Performance Review Cycle. For the calibration process that ensures consistency across managers, see our guide on calibration meetings.

Frequently asked questions

What makes a good performance review comment?

Three elements: observation, impact, and context. Describe what the person specifically did, explain the concrete outcome, and frame it relative to their career level expectations. Generic phrases like 'great team player' carry no weight in calibration or promotion discussions and are legally indefensible if challenged.

How do you write constructive feedback without making it personal?

Focus on observable behaviors, not character traits. 'You raised your voice and talked over two colleagues' is actionable. 'You are too aggressive' is a personality judgment that invites defensiveness. The SBI model from the Center for Creative Leadership provides a reliable structure for separating behavior from interpretation.

How many performance review examples should you include per competency?

Two to three per competency area per performance level. More than that becomes repetitive. Each example should reference a specific situation with measurable impact. Pull from goal tracking data, project outcomes, and peer feedback collected throughout the review period. Harmny aggregates this evidence automatically for each employee.