Peer feedback examples your team can actually use.

Peer feedback works best when it sounds like something a real teammate would say. It should point to a specific behavior, explain the impact, and make the next step clear. Vague comments like "great job" or "communicate better" are easy to ignore. Specific comments help people repeat what is working and adjust what is getting in the way.

Positive peer feedback examples

• You did a great job turning an unclear project brief into a simple plan the team could follow.
• Your notes after the customer call helped everyone understand the real problem faster.
• I appreciated how you invited quieter people into the discussion during planning.
• The way you handled that production issue kept the team calm and focused.
• Your design review feedback was specific and kind, which made it much easier to act on.

Constructive peer feedback examples

• When requirements change late, it would help if you flagged the tradeoffs earlier so the team can adjust scope.
• In meetings, some decisions are moving quickly. Pausing to summarize the decision would help everyone stay aligned.
• Your ideas are strong, but they sometimes arrive after implementation has started. Bringing them up earlier would reduce rework.
• When Slack threads get long, moving the conversation into a short call could help us resolve blockers faster.
• I would benefit from more context when you ask for changes, especially what customer or business goal the change supports.

Peer feedback request examples

Feedback is not only something you give. Teammates should also be able to request it when they want a clearer view of how they are doing.

• What is one thing I did well during the last sprint that I should keep doing?
• Where could I have communicated more clearly during this project?
• What is one behavior that would make me easier to collaborate with?
• Did my work on this project help unblock the team? If not, what could I improve next time?
• What should I focus on before my next one-on-one with my manager?

A simple peer feedback formula

Use this structure when someone is unsure what to write:

• Observation: What did you notice?
• Impact: Why did it matter?
• Suggestion: What should continue or change?

When to give peer feedback

Peer feedback should not be saved only for formal review cycles. It is often most useful right after a project, presentation, customer call, incident, planning session, or difficult collaboration moment. Timely feedback gives the recipient more context and makes the next action easier.