Peer Review Examples: 60+ Phrases for Feedback

Peer review examples are specific, ready-to-use phrases that help employees give meaningful feedback to coworkers during performance evaluations. Unlike manager-led reviews, peer feedback captures the day-to-day reality of how someone works — their communication habits, reliability under pressure, and willingness to collaborate.

Most people freeze when asked to write a peer review. According to SHRM, nearly 95% of managers are dissatisfied with their review process, and peer feedback is often the weakest link. This guide gives you 60+ peer review examples organized by HR competency, so you can find the right phrase in seconds.

What Is a Peer Review?

A peer review is a structured evaluation where coworkers — not managers — assess each other's performance, skills, and contributions. It's typically part of a broader 360-degree feedback process that gathers input from multiple perspectives.

Your manager sees your work from above. Your peers see it from the trenches. They know who follows through on commitments, who lifts the team during crunch time, and who quietly makes everyone around them better. That's why peer review examples are so valuable — they capture what only colleagues can see.

Why Peer Reviews Matter for Small Teams

In a team of 10–50 people, everyone's contribution is visible. Here's why peer reviews matter even more at smaller companies:

They surface blind spots managers miss. A founder managing 20 people can't observe every interaction. Peer feedback catches the teammate who mentors new hires without being asked, or the one who takes credit for group work.

They build psychological safety. When feedback flows in all directions — not just top-down — people feel safer raising concerns. Research from Google's Project Aristotle found that psychological safety is the single strongest predictor of team performance.

They make feedback more credible. A single manager's opinion can feel subjective. When three peers independently highlight the same strength or development area, the feedback becomes harder to dismiss. This multi-source validation is what makes peer reviews powerful for small teams where every person's growth directly affects the company.

They strengthen retention. People don't leave companies — they leave feeling unseen. Regular peer recognition is one of the most effective employee retention strategies.

How to Write a Peer Review That Actually Helps

Before diving into the examples below, let's establish what separates useful feedback from generic "great team player" comments.

The SBI Framework

The most effective peer reviews follow the Situation-Behavior-Impact (SBI) model from the Center for Creative Leadership:

1. Situation — When and where did it happen?
2. Behavior — What specifically did the person do?
3. Impact — What was the result?

Instead of "Sarah is a good communicator," try: "During the Q3 product launch (situation), Sarah posted daily updates with blockers and wins (behavior), which kept the cross-functional team aligned and reduced meeting time by 30% (impact)."

Five Rules for Better Peer Feedback

• Be specific, not sweeping. "You're great" is a compliment, not feedback.
• Focus on behaviors, not personality. "You interrupted colleagues in three meetings" vs. "You're rude."
• Balance positive and constructive. Aim for a 3:1 ratio.
• Write it promptly. Stale feedback loses its power.
• Make it forward-looking. End with a suggestion, not just a critique.

Peer Review Examples by Category

Below are 60+ peer review examples organized by core HR competencies. Each section includes positive and constructive phrases you can copy and adapt.

Communication Peer Review Examples

Strong communicators keep teams aligned and reduce misunderstandings.

Positive:

• "You consistently communicate project updates before anyone has to ask. During the website redesign, your weekly status emails kept all five stakeholders aligned."
• "You have a talent for explaining complex technical concepts in plain language. Your onboarding walkthrough is something the whole team references."
• "In meetings, you make space for quieter team members to share their perspectives by actively asking for input."
• "Your written communication is exceptionally clear. The process docs you created for our QA workflow saved hours of back-and-forth."

Constructive:

• "Sometimes important details get buried in long email threads. Summarizing key decisions at the top would help the team act faster."
• "In cross-team meetings, adjusting technical jargon for non-technical stakeholders would make your updates even more effective."

Teamwork Peer Review Examples

Collaboration isn't about being friendly — it's about making the people around you more effective.

Positive:

• "You jumped in to help the support team during our product launch week, even though it wasn't your responsibility. That initiative sets the tone for our culture."
• "You actively seek feedback on your work before finalizing it, which caught three issues in the proposal before it reached the client."
• "When disagreements arise, you focus on finding the best solution rather than defending your position."
• "You make remote collaboration seamless. Your habit of documenting decisions in shared docs means no one is left out of the loop."

Constructive:

• "Involving others earlier in your process could improve outcomes. Looping in design before building prototypes would save revision cycles."
• "In group projects, delegating more would help the team develop new skills and prevent bottlenecks."

Leadership Peer Review Examples

You don't need a title to demonstrate leadership. These peer review examples recognize people who step up.

Positive:

• "You took ownership of the onboarding process overhaul without being asked. The new checklist reduced new hire ramp-up time from three weeks to ten days."
• "When our team lead was on leave, you naturally stepped into a coordination role — running standups, prioritizing the backlog, and keeping the sprint on track."
• "Your mentorship of junior team members is outstanding. Two people you've coached received promotions this year."

Constructive:

• "Your ideas are strong, but socializing proposals with stakeholders before executing could increase adoption."
• "Sharing your decision-making process more openly would help the team understand why you chose a direction, not just what you decided."

Problem-Solving Peer Review Examples

Positive:

• "When we hit the data migration issue, you mapped out three solutions with pros and cons before the emergency meeting even started. That preparation saved a day of debate."
• "You approach problems with curiosity instead of panic. During the server outage, your systematic debugging identified the root cause in under an hour."
• "You challenge assumptions constructively. Your analysis showed that three targeted fixes would achieve the same result as a complete redesign at a fraction of the cost."

Constructive:

• "When facing ambiguous problems, try breaking them into smaller pieces before seeking input. A rough framework helps the team collaborate more effectively."
• "Sometimes the desire for a perfect solution delays progress. A good-enough solution shipped this week beats a perfect one next month."

Time Management Peer Review Examples

Positive:

• "You haven't missed a single deadline in six months. Your reliability makes planning sprints significantly easier."
• "When priorities shift mid-week, you communicate adjusted timelines immediately rather than silently falling behind."
• "You manage competing priorities exceptionally well. During Q4, you balanced three client projects and an internal initiative without dropping any balls."

Constructive:

• "When you're overloaded, saying 'no' or negotiating deadlines earlier would help the team plan around your capacity."
• "A quick 'I'll get to this by Thursday' acknowledgment on non-urgent messages would help teammates plan their own work."

Creativity and Innovation Peer Review Examples

Positive:

• "Your idea to repurpose customer testimonials as short video clips generated 3x more engagement than our standard case studies."
• "You bring fresh perspectives to brainstorming sessions. The gamification approach you suggested for our employee onboarding process was something none of us had considered."
• "You're willing to experiment and iterate. The A/B tests you ran on the landing page led to a 15% conversion improvement."

Constructive:

• "Adding rough cost/effort estimates when proposing creative ideas would help the team prioritize which ones to pursue first."

Technical Skills Peer Review Examples

Positive:

• "Your code reviews are thorough and educational. You don't just flag issues — you explain why something matters, which helps the whole team grow."
• "The dashboard you built for tracking hiring metrics is used daily by the entire HR team."
• "Your attention to detail in the employee handbook template caught three policy inconsistencies that could have created legal issues."

Constructive:

• "Documentation for recent projects has been thin. Even brief README files would help teammates pick up your work if you're unavailable."

360 Feedback Questions

A peer review asks coworkers for written feedback. A 360 review widens the circle to the person's manager, their direct reports and their own self-assessment, and it usually mixes rating questions with open-ended ones. If you want to run a 360, or just add a few scored questions to your next peer review, start with the 24 questions below. They cover six competencies, with three statements to rate and one open-ended question for each.

Rating scale: 1 = Strongly disagree · 2 = Disagree · 3 = Neutral · 4 = Agree · 5 = Strongly agree

Rating Questions (1–5 Scale)

Open-Ended Questions

• Leadership: What's one thing this person does as a leader that you'd like to see more of?
• Teamwork: Can you describe a time when this person went above and beyond to support a colleague?
• Communication: What's one way this person could improve their communication?
• Problem solving: Describe a complex problem this person helped solve. What was their approach?
• Work ethic: What's one area where this person could be more reliable or consistent?
• Innovation: What's one skill or area you'd encourage this person to develop further?

Keep about three rating questions for every open-ended one. Ratings are quick to answer and easy to compare from one cycle to the next, while written answers take longer but explain the story behind a score. Ask reviewers to back each answer with one example, using the SBI framework above.

How to Run a Lightweight 360 on a Small Team

1. Decide what it's for. Write down two or three goals, such as spotting leadership potential or improving collaboration, and say up front that results are for development, not pay or promotion decisions. The moment people think peer ratings affect raises, honesty disappears.
2. Pick four to eight reviewers per person. That usually means one manager (or founder), two to four peers who work closely with them, one or two direct reports if they have any, plus a self-assessment. Leave out anyone who has worked with them for less than three months.
3. Brief the team and keep the survey short. Explain why you're doing it, how anonymity works, when the deadline is (give 7–10 business days) and what happens with the results. Stay under 35 questions, and trim to around 20 if people are reviewing more than three colleagues.
4. Collect anonymously and group the results. Use an anonymous form or survey tool rather than passing spreadsheets around. For each person, report the average score per competency, themes from the written answers, gaps between their self-ratings and everyone else's, and their top three strengths and development areas. Never share raw individual responses.
5. Debrief in a one-on-one. Within two weeks, book 45–60 minutes in a one-on-one meeting to cover strengths first, then development areas with specific examples, and agree two or three goals for the next quarter. Check in on progress four to six weeks later. For most small teams, running a 360 twice a year is enough, and quarterly is the most reviewers can sustain.

360 Feedback Template

Copy this form into whatever survey tool you use, then paste in the questions above.

360 feedback for: [Colleague's name]

Your relationship: [Manager / Peer / Direct report / Self]

Review period: [H1 2026 / etc.]

Instructions for reviewers: Rate each statement from 1 (Strongly disagree) to 5 (Strongly agree). For open-ended questions, give a specific example from the review period. Your answers are combined with other reviewers' and grouped by theme, so individual responses are never shared.

Sections (three ratings + one open-ended question each): Leadership · Teamwork · Communication · Problem solving · Work ethic · Innovation

Total: 18 rated questions + 6 open-ended questions = 24 questions

Negative and Constructive Peer Review Examples

Delivering critical feedback is uncomfortable, but avoiding it doesn't help anyone grow. Here are peer review examples that address real issues without becoming personal attacks:

The pattern: describe the observable behavior, state the impact, and open the door to a conversation.

Peer Review Examples Template

Use this copy-paste template for your next review cycle:

Peer Review for: [Colleague's name] Reviewed by: [Your name] Review period: [Q1 2026 / etc.]

1. Top Strengths (2–3 specific examples)

• [Describe what they do well, with a specific situation and impact]

2. Growth Opportunities (1–2 constructive suggestions)

• [Describe the behavior you'd like to see more/less of, and why it matters]

3. Overall Summary [2–3 sentences capturing your overall assessment. Balance honesty with encouragement, and reference specific contributions from the review period.]

This template works well when paired with a performance review tool that collects and organizes feedback from peers automatically.

Tips for Giving Honest Peer Feedback

Write it for your future self. Before submitting, ask: "Would I want to receive this?" If it would sting without being helpful, revise it.

Separate the person from the behavior. "The report had several data errors" is feedback. "You're careless" is a character judgment.

Don't save it all for review season. Real-time peer feedback carries more weight than comments about something that happened months ago.

Follow up. If you gave constructive feedback, check in a month later. Closing the loop reinforces growth.

Tiny Team offers one-time lifetime access to HR and Document Spaces per organization. Choose one module or buy several in a single payment. Each module has its own 30-day free trial, starting when you activate it. No credit card, automatic charges or per-person fees. See current module pricing.

Frequently Asked Questions

What should I write in a peer review?

Focus on specific behaviors you've observed, their impact, and actionable suggestions. Use the SBI framework (Situation-Behavior-Impact) to structure your feedback. Include both strengths and growth areas, backed by concrete peer review examples rather than general impressions.

How many peer review examples should I include?

Aim for 2–3 specific strengths and 1–2 constructive suggestions. A review with three detailed observations is far more valuable than ten vague comments like "great work" or "needs improvement."

How do you give negative feedback in a peer review?

Address the behavior, not the person. Describe what you observed, explain the impact, and suggest an alternative. For example, instead of "You're disorganized," try something like: "When project files aren't in the shared folder, the team spends extra time searching. Using our shared drive consistently would help everyone stay efficient."

What's the difference between a peer review and a 360 review?

A peer review collects feedback only from coworkers at the same level. A 360 review gathers input from peers, the person's manager, their direct reports, their own self-assessment, and sometimes external contacts. Peer reviews are simpler to administer, while 360 reviews provide a more comprehensive picture. Both differ from a manager's performance review, which measures work against goals and often feeds pay decisions. Peer and 360 feedback focus on behaviors, skills and working relationships, so they work best for development, and many teams use them alongside formal reviews.

Should 360 feedback be anonymous?

Yes. Anonymity is what keeps 360 feedback honest, especially on small teams where relationships are close. Without it, reviewers tend to avoid constructive criticism. On a team of eight, people can often guess who wrote what, so only report a reviewer group, such as peers or direct reports, separately when it has at least three people (otherwise fold its answers into the overall scores), and group written comments by theme rather than listing them one by one.

How often should teams conduct peer reviews?

Most teams run formal peer reviews quarterly or semi-annually, aligned with their performance review cycle. Encouraging informal feedback on a continuous basis — through quick messages or dedicated feedback tools — produces better results than relying solely on scheduled reviews.