How to Write Effective Performance Review Comments (25+ Real Examples)
Performance reviews live and die by the comments section. A generic "good job, keep it up" tells an employee nothing. A thoughtful, specific comment can unlock professional growth.
In this guide, I'm sharing exactly how to write comments that actually change behavior. I've included 25+ real examples you can adapt for your team.
Why Performance Review Comments Actually Matter
Here's what most managers get wrong. They think the rating is the feedback. It's not. The rating is the score. The comments are the why.
The core insight: Companies with specific, actionable feedback see 15% higher engagement in the next review cycle. Comments that cite concrete examples see 3x more behavioral change.
When you give someone a 3 out of 5 but don't explain what needs to improve to reach 4, you've told them nothing useful. They leave the review confused. Maybe they think it was fair. Maybe they think you don't like them. Either way, no growth happens.
Your job is simple. Make the employee understand (1) what they did well, (2) where they fell short, and (3) what specific action changes things. That's it.
The Structure That Works: The "What, Why, How" Framework
Good performance review comments follow one simple structure:
- What - The specific behavior or outcome you observed
- Why - Why it matters to the role, the team, or the company
- How - The specific action to improve (if it's critical feedback)
This sounds formulaic because it is. That's the point. Consistency eliminates emotional defensiveness.
What (The Observation)
Be specific. Not "You were a great communicator." Instead: "In the Q3 planning meeting, you clearly explained the budget implications of each proposal."
Not "Your work quality slipped." Instead: "The May report had three calculation errors that required a rewrite."
Why specificity matters:
- Proves you actually observed them, not just handing out generic praise
- Makes it defensible if they push back
- Makes it actionable for them to repeat or fix
Why (The Impact)
Connect the behavior to something they care about:
"This matters because it prevents team misalignment that derails projects"
"This matters because accuracy builds trust with our biggest clients"
"This matters because clear communication saves engineering weeks of rework"
Avoid: "Because that's what we expect" or "Because it's your job." Those aren't real reasons. Real reasons connect to values, outcomes, or mission.
How (The Action)
Only include this for critical feedback or growth areas. Praise doesn't need an action. The action is "keep doing it."
For improvement areas, be specific about what different looks like.
| Not Specific Enough | Specific & Actionable |
|---|---|
| "Improve your communication" | "In your next project kickoff, send a pre-read email the day before. Preview the timeline, highlight dependencies, and list what you need from each team member." |
The more specific, the more likely they'll actually do it.
25+ Examples by Category
Positive Examples (Meets or Exceeds Expectations)
Communication & Collaboration
1. "You took the initiative to schedule weekly syncs with the design team to unblock the product roadmap. This prevented the miscommunication that killed our Q2 timeline last year. Keep doing this with cross-functional work."
2. "In the budget review, you asked clarifying questions before supporting the proposal. It surfaced that we'd missed $200K in annual overhead. That's the kind of thinking that makes you invaluable in planning conversations."
3. "You onboarded three new hires this quarter. Each one mentioned you were the person who made them feel confident to ask questions. That sets the tone for our whole team."
Execution & Results
4. "The new customer success workflow you designed reduced support tickets by 28%. More importantly, you got the team to actually adopt it. Adoption failure is why the last workflow died. That's a different skill."
5. "You completed the rebranding project two weeks early without quality slippage. The timeline pressure was real, but you didn't cut corners on brand consistency. That matters."
6. "Your error rate on the data pipeline dropped from 1.2% to 0.3% this quarter. That's not luck. You redesigned the validation logic. This is how compounding improvements happen."
Ownership & Initiative
7. "You noticed the onboarding checklist was out of date and rewrote it without being asked. Three months later, new hires are onboarding 40% faster. More people need your eye for process problems."
8. "When the API vendor changed their authentication method, you owned the update end-to-end instead of waiting for tech to lead. That's ownership thinking."
9. "You mentored two junior engineers on their pull requests this quarter. Both mentioned you gave specific feedback instead of just pointing out bugs. Keep investing there."
Strategic Thinking
10. "In the pricing discussion, you connected the dots between churn data and our price point. Everyone felt it was a pricing problem. You figured out it was a positioning problem. That kind of thinking saves us from solving the wrong problem."
11. "You pushed back on the timeline for the platform migration. You were right. The original plan would have caused production incidents. Pushing back when necessary takes courage."
12. "You suggested we consolidate three customer data sources instead of building a new integration. It costs $40K less and runs faster. That's engineering thinking applied to product decisions."
Critical / Developmental Feedback (Needs Improvement)
Missing Ownership
13. "In the Q3 project, I noticed you waited for direction on several tasks instead of defining the approach yourself. This role requires you to identify what's needed and propose a path forward. Next time, bring three options to me. Don't wait for me to ask for them."
14. "The launch was delayed because documentation wasn't ready. You knew documentation was on the critical path. Next quarter, flag blockers like this three days out. Don't wait until the day before to mention it."
Execution Gaps
15. "Your code reviews are technically solid, but you're missing edge cases 40% of the time. This is costing the team rework. Start by running the code locally before approving. That catches 70% of edge case issues. Let's check in on this in 30 days."
16. "The presentation to the board had the right data but was hard to follow. You jumped between topics. Next time, spend 30 minutes on structure before building slides. Use the 'three main points' rule. Don't try to cover everything. I'm happy to review a draft version this time."
17. "Your estimates for the backend work have been off by 40% on average. This makes planning impossible. Before the next sprint, let's do a retro. Pick three past projects and break down where your estimate missed. That pattern will show us what you're not accounting for."
Collaboration Issues
18. "In the Q3 planning meeting, you didn't share concerns about the timeline with the team. I heard about them later, one-on-one. If you have concerns, raise them in the group. That's how we solve problems as a team."
19. "You've pushed back on feedback from design twice this quarter saying 'engineering can't do that.' You're both right that there are technical constraints, but the tone put them on defense. Next time, start with 'here's what's hard about that from a tech side.' Frame it as a problem to solve together."
20. "You missed the all-hands meeting and the sprint planning session this month. It's harder for the team to operate when we don't all know the context. These synchronous moments matter. It's okay to miss occasionally, but make it rare."
Strategic Gaps
21. "You suggested three separate tools to solve the workflow problem. Each would work fine in isolation. But you didn't consider how they'd integrate. Next time, think about the downstream effects before proposing a solution. What does it look like six months after implementation?"
22. "You're focused on shipping features faster. That's good. But you didn't mention testing, documentation, or how this affects the support team. Speed matters, but completeness matters too. When you propose a timeline, make sure all the work is included."
Mixed Feedback (Both Strengths & Growth Areas)
High Performer with One Gap
23. "You're one of our strongest engineers. Your code quality is exceptional, and your designs are clean. Here's the growth area: you're not documenting your decisions. Future-you and future-engineers need to understand why you chose approach X over approach Y. Add a 'Design Decisions' section to your PRs. This is the thing holding you back from the next level."
24. "Your customer interactions are outstanding. You're patient, thoughtful, and genuinely curious. You're also careful to a fault. Sometimes 'good enough' is the right call, and you're optimizing for perfection. The enterprise customer right now needs an 80% solution in two weeks, not a 100% solution in two months. Can you shift your thinking on this project?"
Solid Performer Ready to Grow
25. "You're reliable and detail-oriented. The team knows that when you take something on, it gets done right. The next growth area: proposing ideas. You're strong in execution mode. We need you to also think like a creator. What should we build? What's broken that you've noticed? Bring me three ideas next month of things you'd like to fix or build. Even one might become a project."
26. "You've improved your code review feedback a lot this quarter. It's specific and helpful now. You're ready for more responsibility. Would you be interested in owning the refactoring roadmap? You'd have autonomy to set priorities and timelines. This is a stretch for you, but I think you're ready."
27. "Your communication has improved significantly. You're clearer in meetings and more direct in writing. The next step: speaking up when you disagree. You're a bit too agreeable. When you think a decision is wrong, we need to hear that before we commit. It's okay to disagree with the team."
Common Mistakes to Avoid
| Mistake | Example (Bad) | Better Approach |
|---|---|---|
| Comparison Comments | "You're not as strong as Sarah on this skill." | "This role requires X proficiency. You're currently at Y. Here's the specific gap." |
| Vague Praise | "You're a great team player." | Be specific enough that someone could screenshot it. |
| Surprises | Critical feedback with no context | "As we discussed in our Sept 15 one-on-one, the project timeline was delayed because..." |
| Emotional Language | "You seemed frustrated in the meeting." | "In the planning meeting, you didn't ask questions or offer input." |
| Mixing Feedback | Using reviews to address immediate behavioral issues | Address real problems now. Reviews are for patterns next quarter. |
Key rule: No one has ever improved because of vague praise. Be specific enough that someone could screenshot your comments and know exactly what you meant.
Templates You Can Use
Positive Feedback Template
"[Specific behavior you observed]. This matters because [the impact]. I'd like to see you apply this approach to [related area] as well."
Example:
"You scheduled a retro meeting with the customer after the Q3 launch to understand their concerns. This matters because it builds trust and gives us data to improve. I'd like to see you apply this approach to early-stage customers, not just ones with issues."
Critical Feedback Template
"[Specific observation]. I'd like to see you [specific action] next time. Here's why: [the impact]. Can we check in on this in [30/60 days]?"
Example:
"The documentation for the authentication module wasn't complete when we shipped. I'd like to see you finish documentation before you mark the feature done. Here's why: support gets overwhelmed with questions when customers try to integrate without docs. Can we check in on this in 30 days?"
Growth Feedback Template
"You're strong in [area]. The next growth area is [area]. Here's how we develop it: [specific action or project]. I see you ready for this because [reason]."
Example:
"You're strong in technical execution. The next growth area is strategic thinking about business impact. Here's how we develop it: I'm having you own the roadmap planning for next quarter. I see you ready for this because you've shown good judgment in what to build and what to skip."
How to Have the Conversation
Writing the comments is half the work. Delivering them well is the other half.
- Start with strengths. Always. Two specific strengths before any critical feedback.
- Deliver critical feedback neutrally. Don't soften it with filler language, but do frame it as fixable.
- Be quiet after you speak. Let them respond. Don't over-explain.
- Ask what they think, not if they agree. "What's your take on this?" opens conversation. "Do you agree?" closes it.
- End with next steps. "Here's what improvement looks like. Here's how I'll support you. Let's check in in 30 days."
The Real Test
Before you hit save on a performance review comment, ask yourself: "If an employee read this with zero context, would they know exactly what to do differently?"
If the answer is no, rewrite it.
Vague feedback makes you feel like you're being nice. It's actually cruel. It sends an employee out into the world without a map. Specific feedback feels harder to write, but it's the kindest thing you can do.
Your comments might be uncomfortable to write. That's a sign you're doing it right.
FAQ
How long should performance review comments be?
Long enough to be specific. 2-3 paragraphs for most feedback. If you're writing more than a page per comment, you're probably covering multiple issues that should be separate conversations.
What if an employee disagrees with my feedback?
That's what the review conversation is for. If you've been specific and cited concrete examples, you can have a real discussion. If you've been vague, they can't push back on anything specific.
Should I write different comments for different performance levels?
Yes. High performers need growth feedback (stretch projects, new skills). Solid performers need clarity on where they excel and one growth area. Struggling employees need very specific, documented feedback about what needs to change and by when.
How often should I write performance comments?
Formally, at review time. But the feedback in those comments should never be a surprise. You should be having these conversations in one-on-ones throughout the year.
What if I can't think of specific examples?
That's a sign you haven't paid enough attention to this person's work. You can't rate someone fairly if you don't have examples. If you're stuck, ask your team for input. Just be honest: "I'd like more context on how Sarah handled the Q3 project."
