8 Feedback Examples for Peers You Can Use in 2026

You need to give a colleague feedback, and the hard part usually isn’t spotting the issue. The hard part is saying something useful without making the relationship awkward. “Good job” feels shallow. “You need to improve communication” feels vague. And if you wait too long, small frustrations turn into bigger ones.

Strong peer feedback does two things at once. It helps the other person improve, and it protects trust. That balance matters because peer relationships don’t have the built-in authority of manager-to-report conversations. You’re speaking to someone you work alongside, depend on, and often need to keep collaborating with the next day.

There’s a reason structured peer feedback keeps showing up in strong performance systems. Google’s use of OKRs with 360-degree feedback gave weight to input from juniors, peers, and managers, and that peer-inclusive approach has been linked to long-term scale and accountability, according to Terryberry’s write-up on peer evaluation examples. For everyday teams, the practical lesson is simple. Feedback works better when it reflects real day-to-day collaboration, not vague top-down impressions.

You also don’t need to guess whether peer feedback matters. Organizations using 360-degree peer reviews see higher engagement and greater productivity gains than teams using traditional reviews, according to Workhuman’s summary of Quantum Workplace findings. Structured peer feedback also helps people act on what they hear, instead of filing the conversation away and changing nothing.

That’s where good frameworks help. They give you a way to talk about behavior, impact, and next steps without drifting into personal judgment. Below, you’ll find practical feedback examples for peers that you can adapt for praise, course correction, missed deadlines, teamwork friction, and follow-up planning.

1. SBI Model

If you only learn one method, learn SBI. It stands for Situation, Behavior, Impact. It works because it forces you to separate what happened from what you felt about it.

Most peer feedback goes wrong when someone skips straight to interpretation. “You were dismissive.” “You weren’t collaborative.” “You don’t communicate well.” Those lines invite debate. The other person starts arguing about intent, tone, or fairness instead of listening to the point.

How to say it cleanly

SBI keeps you anchored in facts.

Situation names the moment. Behavior describes what you observed. Impact explains the result on the team, project, or customer.

Try these feedback examples for peers:

• Missed input in a meeting: “In yesterday’s scope meeting, when Sarah asked for your input and you stayed silent, we left without a decision. That pushed the timeline back and left the team unclear on next steps.”
• Strong support under pressure: “When the client issue escalated last Tuesday, you stayed late to document the workaround. That gave the rest of us a clear path to respond and kept the handoff organized.”
• Unclear async update: “In the project channel on Thursday, your update listed completed tasks but not blockers. That made it harder for the rest of us to plan dependencies.”

The reason structured frameworks like SBI work so well is straightforward. They focus feedback on observable actions instead of subjective labels, which improves clarity and reduces bias, as explained in Leapsome’s overview of peer review feedback frameworks.

Practical rule: If your sentence includes a personality label, rewrite it until it describes behavior instead.

What works and what doesn't

SBI works best when the behavior is specific and recent. It also works when you’ve done enough homework to name the impact clearly. Don’t stretch for impact if you don’t know it. Keep it honest.

What doesn’t work is padding the message with assumptions. For example:

• “You didn’t care about the meeting.”
• “You were trying to block the decision.”
• “You always ignore people.”

Those aren’t observations. They’re guesses.

A strong prep routine looks like this:

• Write the situation first: Note the meeting name, date, Slack thread, customer call, or review cycle.
• Describe visible behavior only: Stick to words spoken, actions taken, or deliverables submitted.
• Test the impact statement: Ask whether the other person will understand the effect on time, quality, trust, or team flow.

If you use PeakPerf, this is the sort of conversation where guided prompts help. They push you to fill in the missing parts before you speak, which often removes the emotional charge from the draft.

2. Radical Candor

Some feedback fails because it’s too soft. Some fails because it lands like an attack. Radical Candor sits in the middle. You show care for the person, and you still say the hard thing plainly.

This approach matters with peers because you don’t want your honesty to sound like scoring points. You also don’t want your empathy to water down the message so much that nothing changes. Both mistakes are common.

A direct opening often works better than a long setup. You can say, “I value working with you, so I want to be straight about something that’s affecting the team.” That line signals respect, not superiority.

Scripts that sound human

Use care and challenge in the same breath.

• “I like working with you and I trust your judgment. That’s why I want to say this directly. In code reviews lately, your comments have been sharp but not always useful, and I think people are starting to brace for your feedback instead of learning from it.”
• “I’m bringing this up because your work matters here. On yesterday’s client call, your answer shut the customer down before we understood their concern. We need to fix that before the next call.”
• “You’ve got strong ideas, and I don’t want that strength to get lost. In meetings, you often jump in before others finish, and it’s making the discussion narrower than it needs to be.”

Place this visual where a framework snapshot helps the point land.

Where people misuse this model

The biggest mistake is using “direct” as cover for frustration. If you’re irritated, cool off first. Radical Candor isn’t bluntness for its own sake. It’s honesty in service of the person and the work.

The second mistake is opening with fake warmth. People hear that instantly. Don’t say you admire someone if you can’t name what you admire. Keep the care statement specific.

Say the true thing with respect. Don’t hide the message, and don’t swing the hammer.

A few habits make this method land better:

• Lead with something real: Name a strength, contribution, or reason the conversation matters.
• Name one issue clearly: Don’t pile on four months of grievances.
• Leave room for response: Ask, “How did you see it?” and wait.
• Follow up later: A hard conversation without later support feels like judgment, not partnership.

If you want a tone that feels warm without getting vague, a developmental draft in PeakPerf is often the right fit for this kind of message.

3. SMART Goals Framework for Feedback Follow-up

A common peer feedback failure looks like this. Two coworkers have a candid conversation, they both nod, and then nothing changes by the next sprint, next meeting, or next review cycle. The problem usually is not the feedback itself. The problem is that nobody translated it into a clear next action.

SMART goals solve that follow-up problem. They turn a broad comment into a visible commitment: specific, measurable, achievable, relevant, and time-bound. In peer settings, that matters because vague advice creates polite agreement, not behavior change.

Turn vague comments into a plan someone can actually follow

Weak version: “You need to communicate project status better.”

Stronger version: “For the next six weeks, post a written status update every Friday before end of day. Include completed work, blockers, and next week’s priorities.”

Weak version: “You should speak up more in meetings.”

Stronger version: “In the next four team meetings, share at least one risk, recommendation, or decision point before the meeting ends.”

The difference is simple. The stronger version gives the person a behavior, a cadence, and a finish line. That makes follow-up fairer for both sides.

A useful peer script sounds like this:

• “Your work is strong, but blockers are reaching the team late. Would you be open to trying a short weekly update for the next month so we can catch issues earlier?”
• “You have good instincts in meetings. For the next three project reviews, can you raise one concern or recommendation before we wrap?”
• “Your feedback in docs is helpful. Let’s make it more consistent by commenting on the draft before the review meeting for the next two cycles.”

Build the goal with the other person

Do not hand over a polished improvement plan and call it collaboration. Peers usually support what they helped define.

Ask a few direct questions instead:

• Start with one behavior: “What is one change you can test next week?”
• Set the review point: “When should we check whether this is working?”
• Make success observable: “What would I see you doing differently?”

That last question matters. I have seen teams write goals that sound precise but cannot be observed in real work. “Be more proactive” is not a goal. “Send the risk summary before Thursday planning for the next four weeks” is.

If the work does not fit a clean metric, use a clear behavior and a deadline. That is still SMART enough to manage. If you want examples of stronger goal writing, this guide to SMART goals for performance management is a useful reference after the conversation.

PeakPerf helps at this stage because it takes the framework out of theory. You can turn a feedback theme into a development action, set a check-in rhythm, and keep the language consistent across managers and peers. That matters in practice. A model is only useful if people can apply it the same way after the meeting ends.

4. The Start, Stop, Continue Method

You finish a sprint retro, and the feedback starts getting vague. One person says a teammate should "communicate better." Another says they are "doing great." Nobody leaves with a clear next step. Start, Stop, Continue fixes that problem fast.

It gives peers a simple structure for naming one behavior to add, one to reduce, and one to keep. That balance helps the conversation stay useful. You are not stacking criticism. You are showing what is working, what is getting in the way, and what would improve the team’s day-to-day work.

A practical format for fast peer feedback

Keep it tight. One item in each bucket is usually enough. Two can work in a formal review. More than that starts to read like a case file, and peers stop hearing the signal.

Examples:

• Start: “Start flagging risks earlier in planning. You usually spot dependencies before the rest of us, and raising them sooner would help the team adjust before timelines slip.”
• Stop: “Stop booking meetings back-to-back when you’re running the decision. The handoff gets rushed, action items get fuzzy, and people leave with different interpretations.”
• Continue: “Continue writing clear pull request notes. The context shortens review time and helps newer teammates understand why the change was made.”

Where this method works best

Use this model when speed matters and the relationship is fairly equal. It works well in retrospectives, project debriefs, and peer review cycles because everybody already understands the categories. You do not need a long setup. That makes it useful for list-based feedback forms, live conversations, and team sessions where several peers are contributing input to one person.

The trade-off is depth. Start, Stop, Continue is easy to use, but it can get shallow if the examples are generic. “Start communicating better” is not helpful. “Start posting the decision summary in Slack right after client calls” gives the person something they can do.

A few rules keep the method sharp:

• Anchor each point in a repeated workflow: planning meetings, code reviews, standups, handoffs, or customer updates
• Explain the impact of the Stop item: time lost, rework created, decisions delayed, trust weakened
• Make Continue specific enough to repeat: name the habit so it does not sound like filler praise

I use this framework when a team needs a shared language for feedback, not a long coaching session. That is why it works well in practice. It combines a familiar model with ready-to-use prompts people can apply on the spot.

PeakPerf helps here by turning these three buckets into a repeatable feedback habit. Teams can capture patterns across reviews, keep examples tied to real work, and avoid the vague comments that make peer feedback easy to ignore.

5. The Situation, Options, Benefit Model

Sometimes direct corrective feedback puts people on defense too fast. That’s especially true with peers who feel sensitive about visibility, confidence, or communication style. In those moments, I prefer a collaborative frame.

Situation, Options, Benefit works because it shifts the tone from judgment to problem-solving. You still name the issue, but you also offer paths forward instead of one verdict.

Use options to reduce resistance

A peer who hears one prescribed fix often starts arguing about the fix. A peer who hears two or three reasonable options starts thinking.

Example one:

• “I noticed that in the last few planning meetings, you stayed quiet even when the team hit open questions. One option is to prep two talking points before the meeting. Another is to jump in with clarifying questions if you’re not ready with a recommendation. A third is to ask for agenda topics earlier. The benefit is that your thinking gets heard before decisions are locked.”

Example two:

• “In code reviews, your comments focus a lot on style issues. You could prioritize functional concerns first, save style comments for a summary note, or lean more on linting tools for routine items. The benefit is faster reviews and feedback that feels more developmental.”

Why this works with peers

Peers usually want respect as much as direction. Giving options signals that you’re not trying to control them. You’re trying to help them choose a better path.

This is especially useful with first-time leads, strong individual contributors, and quiet high performers. Those groups often react badly to “Here’s what you need to do,” but respond well to “Here are a few ways to handle this.”

Offer real options, not one hidden command with two fake alternatives.

A few rules keep this model honest:

• Bring options you’d accept yourself: If all but one option are weak, the person will notice.
• Ask for their read first: They might propose a better path than yours.
• Frame the benefit around their goals: Visibility, trust, speed, less rework, stronger influence.

PeakPerf is useful here because a supportive tone draft tends to phrase these choices as collaboration instead of correction. That matters when the relationship is equal and ongoing.

6. The Feedback Sandwich

This method gets mocked for good reason. Used badly, it sounds fake. People hear the opening praise, brace for the hit, and ignore the closing line. Still, I wouldn’t throw it out.

In peer settings, the sandwich works when the positive feedback is real, specific, and connected to the criticism. It fails when the praise is filler.

When to use it

Use this structure when trust is still forming, when the issue is sensitive, or when the other person mostly performs well but has one habit that’s getting in the way.

A good example:

• “Your analysis in that report was thorough and your reasoning was easy to follow. One part held it back. The recommendation section came so late that most readers will miss the decision point. If you move your top recommendations to the first page, your work will have more impact. The depth of thinking is there, and that’s why this change matters.”

A bad example sounds staged:

• “You’re great. Here’s a problem. You’re still great.”

The trade-off to watch

The sandwich creates safety, but safety has a cost if you overuse it. People start waiting for the criticism hidden in every compliment. That weakens praise over time.

So use it strategically, not constantly.

• Make the first positive point substantive: Name a real strength or contribution.
• Keep the middle crisp: One issue, one example, one suggestion.
• Let the ending reinforce confidence: Don’t repeat generic approval.

Some teams are overcorrecting toward constant positivity. That’s risky too. A contrarian point worth remembering is that praise without grounded developmental feedback can backfire, according to WorkTango’s article on constructive feedback examples. The practical takeaway is simple. Balanced feedback tends to hold up better than praise-only feedback.

If you’re drafting this kind of note in PeakPerf, the supportive tone usually gives you a cleaner version than writing freehand from memory.

7. The Growth-Oriented Questioning Approach

Not every feedback conversation should start with a statement. Sometimes the better move is a question. Good questions help the other person inspect their own choices before you offer your view.

This approach works best when the peer is thoughtful, self-aware, or already motivated to improve. It’s weaker when someone is avoiding responsibility or when the issue needs immediate correction.

Questions that open a real discussion

Instead of saying, “You missed the deadline,” try this sequence:

• “Walk me through what happened on the timeline.”
• “Where did the plan start slipping?”
• “What would’ve helped you raise the risk earlier?”
• “What will you change on the next project?”

Instead of, “Your feedback was too harsh,” ask:

• “What response were you hoping for with that comment?”
• “How do you think it landed?”
• “How would you phrase it if the goal was the same but the tone was easier to hear?”

This image fits here because the method depends on curiosity, not declaration.

What makes this method hard

Silence. A common pitfall is to ask a good question and then ruin it by answering for the other person. If you want insight, wait. If the person is thinking, don’t rescue them.

This approach also demands preparation. You need a sequence of questions that moves from facts to reflection to next steps. If you ask only broad questions, the conversation drifts.

For managers and team leads who want to strengthen this style, these coaching skills for managers map well to peer feedback too.

The right question does more work than a long lecture.

Remote teams benefit from this approach in a different way. Distributed work creates more room for misunderstanding because peers don’t see body language or hallway reactions. A 2025 Gartner report noted remote workers often report miscommunication from missing non-verbal cues, according to Deel’s article on peer review feedback examples. Questions help you test your read before you harden it into a judgment.

8. The Peer-to-Peer Accountability Framework

Two peers leave a planning meeting annoyed for different reasons. One thinks the other pushed a decision too fast. The other thinks concerns came up too late to be useful. A one-way critique can turn that tension into scorekeeping. Mutual accountability gives both people a fairer path. Each person names one behavior to improve, agrees on how to spot it, and commits to a check-in.

That shift matters in peer relationships. Shared accountability lowers the temperature because both people are under the same standard.

Make the commitments reciprocal

Use a direct opening:

• “I want to get better at flagging project risk earlier. You’ve said you want to leave more space for input in planning meetings. Want to check in on both over the next month?”

Then make the follow-up just as concrete:

• “In today’s roadmap meeting, you asked for reactions before giving your recommendation. That gave the room more space. How did that feel? My side still needs work. I waited too long to raise a dependency risk.”

This framework works well for peers because it deals with a real trade-off. Candor gets easier when exposure is mutual, but the conversation can also get fuzzy if both people stay too polite. Keep the bar specific. Name the behavior, the moment, and the next test.

Keep the structure tight

“Let’s keep each other honest” sounds good and usually goes nowhere. A better version has four parts:

• Choose one growth area each: One behavior is enough to track well.
• Set a check-in rhythm: Every two or four weeks works better than waiting for problems.
• Use one shared model: SBI is useful here because both people can describe what they saw without drifting into motives.
• End with one next step: Each check-in should produce a small behavior change to test before the next one.

That structure is what turns theory into practice. It also makes tools more useful. In PeakPerf, teams can document the commitment, save example phrasing for difficult conversations, and revisit the same behavior pattern over time instead of starting from scratch in every check-in.

If you want a simple follow-up rhythm you can adapt for peer conversations, this guide on how to hold employees accountable maps well to shared peer check-ins too.

8 Peer Feedback Models Compared

Make Your Next Feedback Conversation Count

Good peer feedback isn’t about sounding polished. It’s about being clear enough to help and respectful enough to keep the relationship strong. That takes practice. Many individuals don’t struggle because they lack good intentions. They struggle because they don’t have a structure, so they ramble, soften the point too much, or come in too hard.

If you want a simple place to start, use SBI for your next conversation. It gives you a clean way to describe what happened, what you observed, and why it mattered. If the issue needs more warmth, use Radical Candor. If the person needs a path forward, pair the feedback with a SMART follow-up. If you’re in a team retro, Start, Stop, Continue keeps the conversation fast and balanced.

The bigger point is consistency. Feedback works best when it’s normal, specific, and tied to shared work. Google’s long-running peer-inclusive model is one visible example of that pattern in practice, and the wider lesson applies to smaller teams too. When peers give grounded input based on daily collaboration, the feedback tends to feel fairer and more useful than broad top-down judgment.

Keep your language behavior-based. Keep your examples recent. Keep your next step small enough to follow through. Those three habits solve most feedback problems before they start.

It also helps to match the method to the moment.

• Use SBI when the issue needs precision.
• Use Radical Candor when trust matters and the message is hard.
• Use SMART goals when you want the feedback to change behavior.
• Use Start, Stop, Continue when you need a balanced format.
• Use Situation, Options, Benefit when you want collaboration instead of correction.
• Use the sandwich carefully when the relationship is still new.
• Use questions when reflection will work better than a speech.
• Use mutual accountability when both people are committed to growth.

One more trade-off matters. Don’t chase a perfect script. Prepared is good. Over-rehearsed is not. If your language sounds too polished, the other person may stop hearing the human intent. Write your main points down, but speak like a coworker, not a policy manual.

For teams building a stronger review culture, it also helps to look at broader question sets beyond one-off conversations. This collection of Top 100 Essential 360 Assessment Questions is a useful reference if you’re shaping peer input for review cycles.

If you want support turning rough thoughts into a clean draft, PeakPerf is one practical option. Its workflows are built around tools like SBI and SMART goals, which helps when you need to prepare quickly for a difficult conversation, development plan, or peer review.

Your next feedback conversation doesn’t need to be perfect. It needs to be honest, useful, and specific enough to help the other person do better work with you tomorrow.

If you want a faster way to prepare feedback examples for peers, PeakPerf helps you turn a blank page into a structured draft for feedback conversations, performance reviews, and development plans. You answer guided prompts, choose a tone, and edit the result before you send or speak.