The anatomy of an effective evaluation comment

Behavior: What did you observe? Example: When did it happen? Impact: What was the result? Not every comment needs all three elements, but the stronger the evidence, the more credible the evaluation.

Top performer comments (exceeds expectations)

Overall performance

  • Consistently delivers work that sets the standard for quality on the team — peers reference their output as the bar to match.
  • Not only met every goal this period but created new value that wasn't in the original scope — the initiative to [specific action] added meaningful impact beyond the core deliverables.
  • Operates reliably above their current level — the scope, quality, and autonomy of their contributions reflect what we expect from a [next level title].
  • Has had an outsized impact on the team's effectiveness this period — the combination of high output and team-multiplying behavior is rare.
  • Took on a stretch assignment in [area] and executed it to a higher standard than most experienced team members would have.

Productivity and results

  • Produces more output at higher quality in less time than anyone at the same level — efficiency is a competitive advantage for the team.
  • Delivered [project/initiative] on schedule despite significant scope changes mid-cycle — an impressive demonstration of adaptability and focus.
  • Goal attainment was 100% for the period, with three goals exceeded beyond the original target. What's notable is that this was achieved while also supporting two teammates through their deliverables.
  • Manages their workload with unusual discipline — rarely overcommits, consistently delivers, and flags risks early when they arise.

Leadership and influence

  • Has become a de facto technical lead for [area], even without the title — colleagues on other teams seek their input, and the quality of cross-functional decisions has improved as a result.
  • Led the [initiative] from definition to delivery — drove alignment across three teams on a problem that had been stalled for months.
  • Actively invests in the team's growth: documented [X], mentored [colleague], and ran two knowledge-sharing sessions this quarter. This is team-health work that rarely shows up in output metrics.
  • Makes decisions at exactly the right scope — never over-escalates decisions within their authority, and reliably surfaces decisions that need broader input.

Solid performer comments (meets expectations)

Overall performance

  • Met commitments consistently and contributed positively to the team's output — a reliable contributor at the expected level.
  • Delivered on all core responsibilities with appropriate quality and minimal rework required.
  • Performance this period is consistent with expectations for the level — shows steady execution and good judgment in familiar territory.
  • Demonstrated sound judgment in [specific area] and delivered the expected outcomes without requiring significant management direction.

Specific competencies

  • Communication is clear and timely — the team is regularly informed of progress and blockers without needing to ask.
  • Works effectively with cross-functional partners and maintains productive working relationships even when priorities conflict.
  • Approaches problems methodically — solutions are well-reasoned and consider second-order effects.
  • Takes clear ownership of assigned work and follows through until outcomes are achieved, not just until tasks are complete.
  • Handles feedback constructively and applies it consistently — the improvement from [previous review period] in [specific area] is visible and meaningful.

Development-needed comments (below expectations)

These comments should never be surprises — they should echo conversations that have already happened. Frame as development, be specific, and always include what improvement looks like.

Output and delivery

  • Goal completion this period was below the expected level. Three of five goals were completed; the remaining two were in flight at period end. To close this gap: [specific action]. We'll revisit at 60 days.
  • Output quality has been inconsistent — some deliverables are excellent, others required significant revision. Developing a consistent quality check before handoff would reduce rework for the team. Specifically: [what that looks like].
  • Timelines have slipped more often than expected this period. This isn't about speed — it's about improving early-warning signals so blockers surface while there's still time to act on them.

Communication

  • The team has sometimes learned about blockers after they've affected timelines. More proactive updates — even brief — would give the team time to help and prevent avoidable delays.
  • Written documentation and handoffs have required follow-up clarification more than expected this period. Investing in clearer written communication would save the team significant time. A useful target: documents that don't require a follow-up Slack message.

Collaboration

  • There have been several instances this period where working independently when collaboration would have been faster led to rework. The habit to develop: check "who else should know about this?" before finalizing independently.
  • Feedback from cross-functional collaborators suggests that disagreements occasionally escalate rather than converge. Practicing the pattern of acknowledging other perspectives before advocating for a position would improve cross-team relationships meaningfully.

Development and growth

  • The development goals from the previous review period have not been substantially advanced. Let's diagnose together whether this is a priority, capacity, or support gap — and reset with a more specific plan.
  • Feedback has not always landed visibly. We've discussed [specific area] multiple times, and the behavior continues. This is the primary area of focus for the next period: [specific improvement indicator].

Comments for specific situations

Promotion decision — strong yes

  • Has been operating at the [next level] for two consecutive quarters. Promotion is the right recognition of work that is already happening — this is a calibration to reality, not an investment in potential.
  • The case for promotion is clear: [specific evidence for each criterion]. Strong recommendation to proceed.

Promotion decision — not yet

  • The technical quality is there; the remaining gap for [next level] is in [specific area]. The focus for the next 6 months should be [specific development action]. With consistent progress here, promotion is the logical outcome.
  • A strong contributor at the current level. Promotion requires demonstrating [specific capability] consistently — this is the development focus for the next period.

New team member (first review)

  • Has ramped faster than expected — was contributing independently within [timeframe] and has built strong working relationships across the team.
  • A promising start. The areas to develop now that the fundamentals are in place: [specific areas]. Good foundation to build on.

Long-tenure employee

  • Institutional knowledge continues to be an asset to the team — the ability to provide context and historical perspective that junior members don't have accelerates decision-making.
  • Has maintained consistent performance over an extended tenure. To ensure the role continues to offer growth, the focus for the next period is [specific stretch area].

What to avoid in evaluation comments

Avoid Use instead
Is a team player Consistently unblocks teammates without being asked, as shown when...
Needs to be more motivated Output in [specific area] has been below expectations; diagnosing what's driving this is the first step
Always / never On [date/project], X happened. This has been a recurring pattern in [timeframe]
Difficult to work with Feedback from cross-functional collaborators indicates that [specific behavior] has created friction
Has a bad attitude [Specific observed behavior] has been interpreted negatively by some colleagues — worth discussing directly
Is a natural leader Led [project] without formal authority, getting alignment from three teams on a stalled problem
Would be great at next level At next level, core responsibility is [X]. The evidence from this period: [specific example]

See also: performance review phrases · self-evaluation examples · how Harmny handles review cycles