50 Peer Feedback Examples for Every Situation (and 10 to Stop Using)

You owe three peer reviews by Friday. Everything you've typed so far says "great team player." Delete it! Your colleague can't do anything with that sentence.

That's the problem with most peer feedback: it's vague enough to feel safe and useless enough to be forgotten by Monday. Effective peer feedback names one specific situation, the behavior you observed, and the impact it had on the team, nothing more, nothing less.

Below are 50 curated examples, organized by competency and by the situations that make peer feedback genuinely hard to write -the awkward ones, the "how do I say this nicely" ones, the ones you're avoiding right now.

Keep reading!

What Is Peer Feedback?

Peer feedback is the input colleagues at a similar level give each other about specific work behaviors, based on direct experience of working together. It runs through 2 formal channels, peer review cycles and 360 degree feedback, and 1 informal one: the everyday comments teammates trade between cycles. It can be named or anonymous; that choice decides how honest it gets.

Peers see what managers never do.

Only 25% of employees strongly agree they receive valuable feedback from the people they work with, but those who do are five times as likely to be engaged.

Formal reviews happen once or twice a year but the skill behind them is built daily.

How to Write Peer Feedback That Lands (the SBI Rule)

Effective peer feedback names one specific situation, describes the observed behavior, and states its impact on the team, which is why the SBI (Situation-Behavior-Impact) model is the default structure for peer reviews. Most of us are out of practice: only 23% of employees strongly agree they received meaningful feedback in the past week.

The fix is 3 actionable rules.

Positive Peer Feedback Examples

Positive peer feedback works best when it names the exact behavior a colleague should repeat, not just that they did well.

Peer recognition is uncommon in most workplaces. Just 15% of employees receive weekly recognition from peers, versus 29% from managers.

Sharing praise publicly adds another benefit: it sets a visible example. On a social recognition feed like Vantage Recognition's, one specific comment can show the whole team what good work actually looks like.

(Source: Vantage Recognition)

These 18 examples double as feedback for colleagues examples for any teammate.

Communication and Collaboration

These 6 examples reward clarity that saved someone time.

1. "Your API walkthrough in Tuesday's standup saved me a day of reverse-engineering the docs."
2. "You caught marketing and product using different launch dates. That flag prevented a missed deadline."
3. "Your summary of both sides of the pricing debate let us decide in one meeting."
4. "You asked the question everyone was avoiding on the client call, and the answer improved our scope."
5. "Your meeting notes are the only ones I never double-check. The action items always match."
6. "When the handoff got messy, you picked up the phone. The issue closed that afternoon."

Reliability and Quality of Work

These 6 examples name the dependable behaviors peers notice first.

7. "Every file you sent this quarter was final-draft quality. I stopped budgeting review time for them."
8. "You delivered a day early, giving QA a full extra day. The release went out clean."
9. "Your test cases caught the edge case we all missed. That bug would have reached customers."
10. "You flagged the contract risk before signing. Legal confirmed it would have cost us the exit clause."
11. "Your dashboard answers the three questions leadership asks every Monday. Nobody chases those numbers anymore."
12. "You kept the migration checklist current, so the night shift resumed exactly where we stopped. Zero rework."

Supporting Teammates and Culture

These 6 examples recognize the work that holds a team together.

13. "You stayed late to rehearse the demo with me. The client raised half the objections we expected."
14. "Your onboarding doc cut the new analyst's ramp-up from three weeks to one."
15. "You credited the intern's idea by name to leadership. She has spoken up ever since."
16. "During the 6 pm outage, you ran the incident channel so the on-call engineer could focus."
17. "You check workloads before assigning, not after. Nobody on this project burned out during crunch."
18. "Your code review questions teach rather than gatekeep. Juniors learn more from them than from the style guide."

Constructive Peer Feedback Examples

Constructive peer feedback is harder to write than praise because it risks damaging the relationship. The fix is structure- pair one observed behavior with a forward-looking suggestion, so the message reads as help rather than a verdict.

The 17 examples below follow that structure, addressing real problems without putting a colleague on trial.

If you need feedback language for situations beyond peer reviews, our constructive feedback examples hub covers every other workplace scenario.

Communication Habits

These 6 examples redirect how a colleague shares information.

19. "Your updates surface only when asked. A two-line Friday status would keep dependencies from stalling."
20. "Your emails put the request in the last paragraph. Leading with the ask would get faster answers."
21. "In Tuesday's workshop you talked over Priya twice. Letting her land the point would sharpen the debate."
22. "You raise disagreements in direct messages after meetings. Raising them in the room lets us fix things together."
23. "Your client summaries need translating before they can be forwarded. Plainer wording would go straight out."
24. "Decisions made in your threads rarely reach the tracker. Logging them would save the recap meetings."

Deadlines, Ownership, and Follow-Through

These 6 examples address slipped commitments without assigning motives.

25. "The copy deck ran late twice, and design absorbed both delays. Earlier heads-ups would let us reshuffle."
26. "The last two commitments slipped because you take on too much. Saying no earlier protects what you own."
27. "Friday's bug handoff had no reproduction steps and bounced back. A complete ticket costs five minutes, saves a day."
28. "You mark tasks done before the stakeholder confirms. Closing that loop first would stop the reopened tickets."
29. "The client heard the doubled estimate from the project manager, not you. Owning that call keeps their trust."
30. "Your launch runbook lives in your head. Writing it down frees the next launch from your calendar."

Strengths and Weaknesses Balance in Peer Reviews

These 5 examples pair a genuine strength with one growth edge, the balance formal peer reviews ask for.

31. "Your analysis is the team's most rigorous. A directional answer Wednesday often beats a perfect one next week."
32. "Everyone trusts you in a crisis. The same energy pointed at prevention would halve the fires you fight."
33. "Your design instincts are strong and well defended. Inviting critique earlier would turn stakeholders into co-defenders."
34. "You help everyone, sometimes at your own deliverables' cost. Two protected focus hours daily would serve both."
35. "Your product knowledge runs deepest here. Documenting even a tenth would make it a team strength."

Peer Feedback Examples for Hard Situations

The hardest peer feedback is shaped by the relationship, not the competency.

These 15 examples cover the 5 moments peers actually search for help with. For scenarios beyond peers, browse the employee feedback examples library.

Giving Feedback to a Work Friend

Name the friendship first, so honesty does not read as distance.

36. "As your friend I can say it straight: the retro sarcasm reads as dismissive to our newer teammates."
37. "Because we are friends I waited too long to say it: your late Mondays keep landing on me."
38. "Friendship makes this easier to say: yesterday's presentation undersold your work. The hardest part got one slide."

Giving Feedback to a Senior Colleague

Offer the ground-level view seniority cannot see.

39. "A view from the front row: when decisions change after review with no note why, the team reruns old debates."
40. "Yesterday's feedback was this quarter's most useful. One ask: before the deadline next time, so I can apply it."
41. "The room goes quiet after your first take. Going last would show you what the team really thinks."

After a Disagreement or Conflict

Repair the relationship and reopen the question separately.

42. "We disagreed hard on the rollout plan, and your staging concern was right. I have added it to the checklist."
43. "Tuesday's debate got personal and I own my half. The pricing question still stands; can we restart Thursday?"
44. "I quoted your number to the client before we agreed. That was on me; next time I confirm first."

For a Remote Teammate You Rarely See

Distance hides effort and friction; name both.

45. "Your async updates are so complete I never said it: they are why our cross-time-zone handoffs work."
46. "You multitask on mute in video calls, and twice I re-asked decisions you missed. I need your attention."
47. "I see your work only in final form, so the late draft gave no warning. A quick flag lets me adjust."

For a Cross-Functional Partner

Anchor the comment in the shared outcome, not your function's preferences.

48. "Your legal review caught real risks after the campaign was built. At brief stage it would shape, not rework."
49. "Your feature demo wins deals. The setup assumes knowledge our reps lack; a five-minute intro version would multiply its use."
50. "Your team absorbs added scope silently until the sprint breaks. Naming the real cost up front helps us ask for less."

10 Weak Peer Feedback Examples, Rewritten

A weak peer feedback comment fails in one of 3 ways: adjective-only praise, personality critique, or a vague "keep it up" that teaches nothing.

Here are 10 rewritten with the SBI structure, each failure named.

Named or Anonymous? Making Peer Feedback Honest

Anonymity is a design decision that trades accountability for candor, so use it deliberately, not by default.

Employees are split for good reason:

62% believe anonymous feedback encourages honesty, yet 79% suspect colleagues of using feedback to settle personal grudges (LiveCareer, 2025).

Both instincts are right.

The working rule from Vantage Recognition deployments: keep appreciation named and public, where a peer-to-peer recognition feed does its work, and give sensitive input a protected channel. In Vantage Pulse, that protection is enforced by the platform, not by policy. Results for any team or segment stay hidden until enough responses arrive, 5 by default and never fewer than 3, so no answer is traceable to a person. Small groups simply see "insufficient responses."

Anonymity's side effect is volume. Hundreds of open-text comments are unreadable by hand, so an employee survey tool that sorts comments into positive, neutral, or negative and clusters themes turns the pile into patterns a manager can act on.

(Source: Vantage Pulse)

Frequently Asked Questions

Q1. What is a peer feedback example?

A peer feedback example is a short, specific comment one colleague gives another about a work behavior: "Your walkthrough of the API changes saved me a day of rework." Strong examples name the situation, behavior, and impact.

Q2. What are some examples of positive feedback for peers?

Positive peer feedback names a behavior worth repeating: "Your test cases caught the bug we all missed," or "Your onboarding doc cut the new analyst's ramp-up from three weeks to one."

Q3. What are examples of peer review?

Peer review examples include strengths ("your analysis is the most rigorous on the team"), growth areas ("an earlier heads-up on delays would let us reshuffle"), and balanced comments that pair both.

Q4. What are three examples of positive feedback?

Three quick examples: "You delivered a day early, giving QA an extra day." "You credited the intern's idea by name in the leadership review." "Your meeting notes always match what we agreed."

Q5. What is an example of a good peer review comment?

A good peer review comment covers one behavior and its impact: "Your updates surface only when asked. A short Friday status would keep dependencies from stalling."

Q6. What are three positive feedback examples?

"Your call summary locked in next steps and saved a follow-up meeting." "You ran the incident channel so the on-call engineer could focus." "Your code review questions teach rather than gatekeep."

Conclusion

Peer feedback improves fastest on teams where commenting on each other's work is already normal. Among employees who receive feedback and recognition from their manager at least weekly, 61% are engaged.

All you've to do is, start small, and start before review season. Pick one colleague, one specific behavior, and write the two sentences the SBI rule asks for. The 50 examples above are yours to adapt.