8 Peer Review Feedback Examples for 2026

You need to give feedback to a peer. You want to help, not offend. You know the work could improve, but you also know one careless sentence can create tension for weeks.

Most managers and teammates get stuck here. They either soften the message until it says nothing, or they come in too hard and turn a useful conversation into a personal one. Neither works. When feedback stays vague, people leave confused. When feedback feels like a judgment, people get defensive.

Good peer review feedback examples solve both problems. They give you language, structure, and timing. They turn a stressful conversation into a specific one. That matters because avoiding feedback doesn't keep the peace. It lets small misses spread into late projects, repeated mistakes, and frustration across the team.

The fix isn't fancy phrasing. The fix is a model you can repeat. Structured feedback methods have been around for decades. The SBI framework, introduced by the Center for Creative Leadership in 1976, pushed feedback away from vague opinion and toward observable facts, and organizations using it saw a 20 to 30 percent improvement in feedback effectiveness and recipient satisfaction according to the data summarized by Rippling's peer review examples guide.

You'll find eight models below, each with positive, corrective, and developmental peer review feedback examples. Use them in one-on-ones, formal reviews, project retros, and day-to-day conversations. If you also give feedback in code review settings, this guide on how to write clear PR feedback is a useful companion because the same principle applies. Clear comments move work forward. Fuzzy comments slow everyone down.

1. SBI Model

The SBI model is where I tell new managers to start. If your feedback tends to ramble, sound personal, or lose focus, SBI fixes that fast. You name the situation, describe the behavior, and explain the impact.

That simple sequence matters because people can respond to facts. They struggle to respond well to labels like "careless," "passive," or "hard to work with." Those words sound like identity claims, not feedback.

A lot of modern peer review feedback examples borrow this shape, even when they don't label it. The classic Rippling example captures it well: during tight deadlines, someone becomes less approachable, which makes coordination harder. That's the pattern you want. Context first. Observation second. Consequence third.

What to say with SBI

Positive example:

“During last Tuesday’s planning meeting, you raised the risk in the timeline before we locked the sprint. You were specific about the dependency on design. That helped us move work around early and avoid a last-minute scramble.”

Corrective example:

“Yesterday in standup, you said the report would be ready by 3 PM, and it came in at 6 PM. The missed handoff delayed the client presentation and forced the team to reshuffle work late in the day.”

Developmental example:

“In the last two cross-functional meetings, you had strong ideas but waited until the end to raise them. That meant the team made decisions before hearing your input. I’d like you to speak earlier, especially when you see a delivery risk.”

When SBI works best

Use SBI when:

• You need precision: A specific event beats a broad impression.
• You expect defensiveness: Facts lower the temperature.
• You want fairness: The same structure works for praise and correction.
• You need a written draft first: SBI is easy to outline before a live conversation.

Focus on what a person did, not what you think they are.

One trade-off matters. SBI is excellent for clarity, but weak feedback givers sometimes stop at impact and forget the next step. If you say, “this delayed the team,” and then end the conversation, you've diagnosed the issue without helping fix it.

Write down examples as soon as you see them. Include date, meeting, task, or deliverable. Then say the impact and pause. Let the other person respond before you move into problem solving.

2. SMART Goals Framework for Development Feedback

Some feedback lands well and still goes nowhere. The person agrees, thanks you, and changes nothing. That's usually a planning problem, not a motivation problem.

Development feedback needs a target. If someone leaves the conversation with “I should communicate better,” you haven't given them a plan. SMART goals fix that by forcing specifics around what changes, how you'll know, and by when.

Many peer review feedback examples often fall short. They identify a weakness but never turn it into a next move. A useful review doesn't stop at “improve stakeholder communication.” It defines the habit.

From vague advice to a real plan

Weak version:

“Improve communication skills.”

Stronger version:

“For the next 8 weeks, lead the weekly update with a clear agenda, decisions, and action items. At the midpoint, review what’s working and where people still feel unclear.”

Weak version:

“Be more strategic.”

Stronger version:

“By the end of Q2, identify three process improvements in your area, document the trade-offs for each, and present a recommendation with an implementation plan.”

If you want a clean structure for writing goals, PeakPerf’s guide on how to set SMART objectives gives a practical breakdown.

Peer review examples using SMART goals

Positive plus stretch:

“You’ve become the person people rely on for clean project updates. Over the next review cycle, I’d like you to build on that by running the weekly cross-team sync and sending a written summary after each meeting.”

Corrective plus plan:

“You’ve missed a few key handoffs because updates came late. For the next month, send your status update before end of day on Tuesdays and Thursdays, with blockers called out in one section so the team can respond quickly.”

Developmental plus support:

“You have strong execution skills. The next step is broader influence. Over the next quarter, take ownership of one cross-functional initiative and lead the planning conversation from kickoff to final recap.”

• Build ownership: Ask the person to help shape the goal.
• Check halfway through: Don't wait until the end of the cycle.
• Mix skill and output: One goal should improve capability, one should improve results.
• Keep the wording plain: If the person can't repeat the goal from memory, it's too fuzzy.

One caution. SMART goals can become too rigid if you stuff every sentence with metrics and formal language. Use enough structure to guide action, not so much structure that the plan feels bureaucratic.

3. Radical Candor

Some teams don't need softer wording. They need honest wording with respect. That's where Radical Candor fits.

This model works when speed matters and the relationship has enough trust to hold directness. You care about the person, and you don't hide the issue. If either piece is missing, the method fails. Care without challenge turns into avoidance. Challenge without care turns into aggression.

Direct scripts that still respect the person

Corrective example:

“I’m being direct because I want your work to carry more weight. In your presentation, you stated opinions as facts in a few places without showing evidence. That weakened your argument. I know you can do stronger analysis, so let’s tighten your prep process before the next review.”

Developmental example:

“You’ve said you want to lead larger projects. Right now, you interrupt people in meetings when you disagree. That habit will limit your influence. I’m raising it because I think you’re capable of more.”

Positive example:

“You handled the client pushback well. You stayed calm, answered the issue directly, and didn’t overexplain. Keep doing that. People trust concise answers under pressure.”

The trade-off is clear. Radical Candor saves time, but only on teams where people believe feedback isn't a political weapon. That gap matters because existing guidance on peer review often mentions anonymity and privacy, but leaves a major hole around fear, retaliation, and suppressed honesty in competitive teams, as outlined in Yulys’s discussion of peer review feedback gaps.

When to use this model, and when to back off

Use Radical Candor if:

• Trust already exists: The person knows you're for them.
• The issue is recurring: Hints haven't worked.
• The stakes are rising: Leadership readiness, client credibility, team trust.

Don't use this style as your shortcut to “being honest” if your team doesn't feel safe. In low-trust environments, blunt feedback often gets filtered as threat. Then the person debates your tone instead of hearing your point.

If people are afraid of the consequences of honesty, direct feedback won't fix the culture. It will expose the culture.

4. The 360-Degree Feedback Model

A manager sees part of the picture. Peers see different parts. Direct reports see another layer. Customers sometimes see things the team misses entirely.

That's why 360 feedback works when you need a fuller view of someone's impact. Peer input is especially useful for patterns around collaboration, communication, follow-through, and influence across functions. In a 2024 analysis across more than 1,200 organizations, adding peer review feedback into performance processes was linked to a 14 percent increase in engagement, a 12 percent increase in productivity, and 78 percent of HR professionals reported more accurate assessments when peers contribute, according to Deel’s peer review feedback examples and tips.

What good 360 feedback sounds like

Theme from multiple sources:

“Your work gets done on time and to a high standard. Several peers also noted that they struggle to get early visibility into your decisions. The pattern isn't work quality. It's collaboration during the process.”

Another example:

“Direct reports see you as dependable and organized. Peers describe you as hard to loop into cross-functional work. Customers say you’re responsive once engaged. The signal here is not capability. The signal is team access.”

A useful 360 summary doesn't dump raw comments. It groups them into themes, then ties each theme to a development action.

If you're building a process from scratch, PeakPerf’s article on the 360 feedback review process is a practical reference point.

How to run 360 feedback without creating noise

• Frame it as development: People write better feedback when the purpose is growth, not punishment.
• Guide the raters: Ask for examples tied to meetings, projects, handoffs, or decisions.
• Look for patterns: One outlier comment isn't a trend.
• Deliver results privately: Let the person process before discussing action steps.

One common mistake is overvaluing consensus. If five people agree on a theme, pay attention. If feedback conflicts sharply, don't force a fake average. Mixed feedback often points to context. Someone might collaborate well upward and poorly sideways. That's still useful.

Another mistake is running 360s on a team that doesn't trust the process. People then write safe, bland comments, and the exercise turns into paperwork.

5. The Feedback Loop

Annual reviews are often too slow. By the time you document the issue, everyone has lived with it for months. A feedback loop fixes that by turning feedback into a regular operating habit.

The model is simple. Observe the work, share a focused comment, discuss what changes next, and return to the topic later. It works best in weekly one-on-ones, retros, and short project check-ins.

A repeatable structure for check-ins

Try a short sequence like this in your one-on-ones:

• What went well: Name one behavior to repeat.
• What got in the way: Name one issue to improve.
• What changes next: Agree on one action before the next check-in.

Example:

“Your proposal was clear and well researched. Next time, put the recommendation on page one so leaders don't need to search for the decision point. Let's test that format in your next draft.”

Another example:

“You handled the handoff well this week. The one gap was flagging the blocker late. Next week, raise blockers the same day so the team has time to respond.”

What works in ongoing feedback

The strength of a loop is timing. Feedback lands closer to the event, so people remember details and adjust sooner. In a structured peer feedback activity run through FeedbackFruits, students rated the feedback they received at an average usefulness score of 8.2 out of 10 across 150 plus participants, and self-assessed critical analysis improved from 6.7 out of 10 before peer review to 9.1 out of 10 after reflection, according to the FeedbackFruits case study on case analysis and peer feedback.

That example comes from education, but the operating lesson carries over to work. Guided prompts, recurring review, and feedback on feedback improve the quality of what people say.

Short, regular feedback beats a polished annual surprise.

The main trade-off is discipline. Feedback loops fail when managers skip sessions, improvise every conversation, or pile on too many issues at once. Keep each cycle narrow. One repeated strength. One priority gap. One next action.

6. Peer Feedback and Upward Feedback

Peer feedback helps you see how someone works alongside others. Upward feedback shows how leadership decisions land below the title line. Both matter because most team friction doesn't show up in output alone.

A person can deliver strong individual work and still create drag for everyone around them. A manager can hit targets and still leave people unclear on priorities. You won't catch those patterns from top-down review alone.

Peer review feedback examples from the side and from below

Peer feedback example:

“You’re dependable on your own deliverables, and I trust your work quality. Where I struggle is cross-team response time. When requests sit without acknowledgment, the rest of us don't know whether to wait, reroute, or escalate.”

Another peer example:

“You bring strong expertise to planning meetings. I’d like to see you share more of your process with the team, because people often need to reverse-engineer how you reached the answer.”

Upward feedback example:

“You make fast decisions, which helps momentum. The missing piece is context. When priorities change and the reason isn't shared, people feel like the ground moved under them.”

Another upward example:

“You’re supportive in one-on-ones. In group settings, priorities still feel unclear. A written summary after leadership decisions would help the team execute with less guesswork.”

For broader team communication habits, this guide on Internal Communication Best Practices is a useful complement.

How to collect better peer and upward feedback

• Ask behavior questions: “What does this person do that helps teamwork?” works better than “What do you think of them?”
• Protect privacy: People give more honest upward feedback when they don't fear fallout.
• Require response: Recipients should share what actions they'll take.
• Separate signal from friction: Not every complaint points to a leadership issue. Some point to role confusion, process problems, or unresolved conflict.

A hard truth sits here. Anonymous forms don't fix a fearful culture on their own. If your team competes for promotions, avoids disagreement in meetings, or mirrors the manager's views too neatly, the data may be clean but unreliable. In that case, fix trust before you overinterpret the feedback.

7. Developmental Feedback with Growth Mindset Framing

Some feedback shuts people down before the conversation even starts. This usually happens when you describe a person as fixed. “You're not strategic.” “You're not detail oriented.” “You're not leadership material.”

Those phrases corner people. They suggest a trait, not a skill. Developmental feedback works better when you talk about methods, habits, and practice.

Better phrasing for growth

Instead of this:

“You're not detail oriented.”

Say this:

“I noticed three errors in the report. Let's look at your review process and build a checklist before final submission.”

Instead of this:

“You're not strategic.”

Say this:

“This analysis is strong on execution. The next step is stepping back earlier and asking what changes if the market, customer, or cost assumption shifts.”

Instead of this:

“You're bad at collaboration.”

Say this:

“You've got useful ideas, and I think your influence would grow if you pulled others in sooner instead of presenting a finished answer at the end.”

If you want stronger language for these moments, PeakPerf’s article on how to give constructive feedback is a solid reference.

Why this framing changes the conversation

Developmental framing doesn't mean softening the issue. It means naming the gap in a way someone can act on. You still point to the problem. You connect it to a skill path.

Peoplebox’s collection of 70 plus examples highlights this practical style, including feedback tied to time management and productivity, summarized in the same verified dataset that notes a 2026 example set for managers using peer feedback language. The useful takeaway isn't the volume of examples. It's the pattern. Strong feedback points to a process change, not a personality flaw.

• Name the skill: planning, listening, delegation, analysis.
• Name the missed behavior: late updates, weak structure, skipped review.
• Name the next practice: checklist, prep note, meeting recap, peer shadowing.

One warning. Growth language becomes empty if every issue gets wrapped in endless encouragement. People still need clarity. “You haven't mastered this yet” only helps if you also define what better looks like next week.

8. Real-Time Feedback and Micro-Feedback

Not every piece of feedback needs a meeting. Some of the best peer review feedback examples are short enough to say in the hallway, in Slack, or right after a call.

Real-time feedback works because context is still fresh. Micro-feedback works because the person doesn't need to reconstruct the moment from memory. You're pointing to something they did minutes ago, not weeks ago.

Short scripts you can use today

After a meeting:

“Good point on the timeline. Next time, lead with the data first. Your argument would land faster.”

After a client call:

“You handled the budget objection well. You acknowledged the concern before offering options, and that kept the conversation calm.”

After reviewing a document:

“Your analysis is strong. Tighten the opening summary so the recommendation is obvious in the first paragraph.”

Before giving a quick correction, ask permission if the topic is sensitive.

“Can I share one observation from that call?”

That small step lowers resistance because it gives the other person a choice in the moment.

The right use of micro-feedback

Use this model when:

• The event just happened: feedback loses force as memory fades.
• The issue is narrow: one habit, one phrase, one missed move.
• You don't need a full review: a sentence or two is enough.
• You work remotely: written praise and quick course correction replace lost office moments.

One practical advantage of structure shows up here too. Teams that use structured feedback models like SBI saw 21 percent higher profitability and 17 percent lower turnover in a 2023 Gallup report cited in the verified data summary from Rippling’s article, which is one reason these models keep showing up in current management tools and examples.

The trap is overdoing it. If every interaction includes a correction, people stop hearing the signal. Keep micro-feedback heavily weighted toward reinforcement, and save larger patterns for a proper one-on-one.

The fastest way to make feedback feel heavy is to turn every moment into a lesson.

Peer Feedback: 8-Model Comparison

Turn Feedback into Your Management Superpower

The best feedback isn't the most polished. It's the most usable. When someone walks away knowing what happened, why it mattered, and what to do next, you've done your job well.

That's why models matter. They remove guesswork when the topic is awkward, emotional, or high stakes. SBI keeps you factual. SMART turns advice into a plan. Radical Candor helps you speak plainly without becoming harsh. 360 feedback widens the lens. Feedback loops keep growth moving between review cycles. Peer and upward feedback expose blind spots. Developmental framing keeps the focus on skills. Real-time feedback helps people adjust while the moment still feels real.

You don't need to master all eight at once. Pick one. For most managers, SBI is the cleanest place to start because it improves both praise and correction. Then add one more model based on your team's needs. If your reviews stall after good conversations, add SMART goals. If your team moves fast and trusts one another, build toward more candid, direct conversations. If you manage across functions or remotely, bring in peer and 360 input.

The hard part isn't knowing the frameworks. The hard part is using them consistently. Managers often wait for the perfect review cycle, the perfect document, or the perfect wording. That delay costs more than an imperfect first draft. Small patterns get repeated. Tension builds. People guess what success looks like. Clear feedback prevents all of that.

A few habits make the whole process easier. Capture examples when they happen, not weeks later. Separate observation from interpretation. Give positive feedback with the same care you use for corrective feedback. Don't stack five issues into one conversation. Ask the other person how they see the same situation. If peer feedback conflicts with your view, treat the mismatch as useful information instead of a problem to smooth over. Sometimes it points to context. Sometimes it points to trust. Sometimes it shows that your team sees behavior you don't.

You also need to respect the limits of process. Anonymous forms and feedback templates help, but they don't replace psychological safety. If people fear retaliation, competition, or social fallout, the comments you collect won't tell the whole truth. In those cases, your first task isn't collecting more feedback. It's rebuilding enough trust for honesty to show up.

Tools help once the basics are in place. PeakPerf is one option if you want help turning a blank page into a structured draft for feedback conversations, development plans, and reviews. The practical value is structure. You answer prompts, apply frameworks like SBI or SMART, and start from something clear instead of staring at an empty document.

Strong managers aren't born with the right phrases. They practice. They prepare. They say the specific thing at the right time, in a way the other person can use. That's what turns feedback from awkward to actionable. That's what makes people better at their jobs. And that's what makes your team stronger over time.

If you want a faster way to prepare peer review notes, one-on-one talking points, or development plans, try PeakPerf. It helps you turn rough observations into structured, editable drafts using proven feedback frameworks, so you spend less time staring at a blank page and more time leading the conversation well.