The Complete Guide to Peer Feedback & 360-Degree Reviews

Last Updated on August 25, 2026 by Status.net Editorial Team

What Is 360-Degree Feedback? Part 1
Peer Reviews: How They Work Part 2
How to Write a Peer Review Part 3
Common Biases That Distort Peer Feedback Part 4
Writing Peer Reviews by Tone Part 5
360 Feedback Questions Part 6
Upward Feedback (Reviewing Your Manager) Part 7
360 Templates Part 8
Receiving and Acting on 360 Feedback Part 9
Common 360 Review Mistakes Part 10

If you have not yet, start with our complete guide “Performance Reviews: The Complete Guide.”

Some of the most useful feedback in a career comes from the side. Peers often see behaviors that managers miss, because peers are the ones sitting next to the work every day. When companies gather that feedback in a structured way, through peer reviews or a full 360-degree process, the picture of an employee’s year gets richer, fairer, and more honest.

This complete guide covers both peer reviews and 360-degree feedback in depth. You will find what each one is, how they work, how to write feedback that lands well, questions to use in your own 360 process, templates for common scenarios, and example phrases you can adapt for every tone. Read it top to bottom, or jump to the section you need right now.

Part 1What Is 360-Degree Feedback?

360-degree feedback is a review process that gathers input from multiple directions around a single employee. Instead of relying only on the manager’s perspective, a 360 collects the picture from every angle: the employee’s own self-assessment, the manager’s view, peer feedback from colleagues at the same level, and, when the employee leads people, upward feedback from their direct reports.

The four directions each surface something different.

Self. The employee’s own reflection reveals how they see their year, which growth areas they are already aware of, and where they may over-rate or under-rate themselves. The gap between self-perception and other perspectives is often one of the most useful signals in the entire process.
Manager. The manager’s view brings scope, business context, and the long arc of the year. It also carries the blind spots that come from watching an employee mostly during structured moments like 1:1s and team meetings.
Peer. Peer feedback captures the collaboration signals a manager cannot see. Peers observe how the employee shows up in real time, how they handle stress, and how they treat teammates when no manager is in the room.
Direct report. For anyone who manages people, upward feedback surfaces the daily experience of being led by that person. It is often the most useful and the most under-collected signal in the whole process.

Organizations use 360 feedback in several common contexts. Some run it as an annual input to the formal performance review. Some use it as a stand-alone development tool, separate from any rating decision. Some pair it with executive coaching, where the coach helps the leader unpack the feedback and build a plan.

The benefits of a well-designed 360 are real. It produces a fuller picture than any single perspective can, it surfaces blind spots that would otherwise stay hidden, and it strengthens the case for both promotions and performance decisions. When used as a development tool, it often accelerates growth for leaders who were plateauing on the same feedback from their manager alone.

The limits are also real. A 360 is only as good as the questions asked, the anonymity protected, and the synthesis done at the end. Poorly designed 360s can produce a wash of vague comments that offer little to act on. Tightly compensated 360s often shift toward safer feedback, because participants know their words influence pay. And every 360 requires meaningful time from a lot of people, which makes them expensive to run well and quick to skip when the calendar tightens.

Choosing the Right 360 Participants

The panel of reviewers matters as much as the questions asked. A poorly chosen group can make even a well-designed 360 feel unfair or of limited use.

Most 360s work well with six to ten reviewers total, spread across peers, direct reports, and cross-functional partners the employee works with regularly.
A mix of self-nomination and manager selection often produces the fairest panel. The employee names people they work closely with, and the manager adds one or two names to round out the perspective, including someone who may see the employee from a slightly more distant vantage point.
Avoid a panel made up only of the employee’s closest allies. Feedback from people who like the employee the most tends to skew warm, and the report loses some of its diagnostic value.
Include at least one person who has worked with the employee through a hard moment: a deadline crunch, a disagreement, a project that did not go well. Those relationships often produce the most useful growth feedback.
For employees who are new to a role or team, six months of working history is often enough for a peer to offer specific, grounded feedback. Reviewers with less exposure than that may be better served by opting out.

For more, see “What is 360 Degree Feedback? [Questionnaire Template]” and “200+ Examples of 360 Degree Feedback Comments.”

Part 2Peer Reviews: How They Work

Peer reviews collect feedback from teammates at the same organizational level. They often happen at the end of a major project, during a formal review cycle, as part of a 360 process, or through peer nominations that recognize standout collaborators.

The strongest peer reviews follow a clear shape. They open with a concrete strength that describes a behavior the peer has observed. They add a specific example that grounds the strength in a real moment. They surface one honest area for growth, framed constructively. They close with a warm, personal note that would still make sense if the review reached the employee’s own eyes.

Peer reviews often carry more weight than the writer expects. A single peer comment, especially one that appears in more than one review, can shape how a manager sees a team member for months. That weight is one of the reasons writing peer reviews with care matters as much as writing a manager review.

A peer review from Jamie: “Sarah has been my most trusted partner on cross-team analytics work this year. When our sales dashboard broke during the Q3 board prep, she stayed late with me to rebuild the queries and never once made it feel like I owed her one. The one area I would love to see her keep building is speaking up earlier in leadership meetings, because the ideas she surfaces in Slack afterward are almost always the best in the room.”
A peer review from Priya: “Michael brings a thoughtful, deliberate approach to every technical decision he touches. His code reviews have quietly raised the standard for our whole team, and I have learned more from his written comments this year than from any single training I have taken. If I could ask for one growth area, it would be sharing more of that same clarity in the live design conversations, where his voice would carry a lot of weight.”
A peer review from Ravi: “Diego handles pressure with a kind of steadiness that is contagious. During the platform migration in Q2, he was the person on the team who kept the group focused and calm through the two hardest weeks. One area I would gently name for growth is delegation, because he tends to absorb more of the coordination himself than the role really requires.”

Peer Nominations for Recognition Programs

Some organizations use peer input outside the formal review cycle entirely, through peer nomination or recognition programs. A teammate nominates a colleague for a specific moment of excellent work, and the nomination often gets shared publicly in a team meeting or company channel.

These nominations serve a different purpose than a performance review. They are built for celebration, so the tone can stay more exuberant and the detail can stay lighter.

Keep the nomination short, one or two sentences naming the specific moment and the value it created.
Tie the nomination to a company value or team norm when the program asks for it, since that reinforces the behaviors the organization wants to see more of.
Send a copy to the person’s manager even when the program is informal. Recognition that never reaches the manager rarely makes it into the employee’s formal record.

Peer Reviews in Remote and Distributed Teams

Writing a peer review is harder when you rarely share a room, or a time zone, with the person you are reviewing. Remote and distributed teams benefit from a slightly different approach to gathering evidence.

Lean on written artifacts. Pull requests, shared documents, meeting notes, and async project updates capture behavior that would otherwise disappear once the moment passes.
Watch for contributions that async work can hide, like a well-timed comment in a shared doc that unblocked the team, or a thoughtful async response written outside normal hours to help someone in a different time zone.
Be careful about comparing someone’s camera-on meeting presence to their actual contribution. Some of the strongest distributed collaborators do their best work in writing rather than in live discussion, and a fair peer review accounts for that.
When you have not worked closely enough with someone to write a grounded review, say so plainly rather than filling the space with generic praise.

For more, see “450 Examples of Peer Review Phrases for Balanced Feedback,”
“300 Peer Review Examples (Positive & Negative Phrases),”
“300 Peer Feedback Examples,”
“100 Feedback Examples for Peers,”
and “60 Example Phrases for Peer Performance Reviews.”

Part 3How to Write a Peer Review

Writing a peer review is a smaller writing task than a manager review, though the craft is often more delicate. You are writing about someone you sit next to every day. The words will shape their year and may shape their relationship with you afterward. A short, careful process helps.

Step 1: Gather a Few Specific Moments

Before you write anything, take five minutes to think back across the year. Look for two or three specific moments when the peer stood out, whether in a positive way or in an area where you noticed room for growth. A single concrete moment carries more weight than five general adjectives.

Step 2: Pick One Strength and One Growth Area

A strong peer review usually surfaces one clear strength and one clear growth area. More than that dilutes the signal. Choose the strength that matters most for the peer’s role, and choose the growth area that would produce the biggest lift if they addressed it.

Step 3: Follow the “Stay Specific, Stay Kind, Stay Useful” Rule

Every sentence in a peer review can be tested against these three questions. Is it specific enough that the peer can picture the moment? Is it kind in tone, even when the content is honest? Is it useful, meaning would it help the peer grow or would the manager reading it make a better decision? If a sentence fails one of the three, revise or cut.

The Right Questions to Ask After a Job Interview (Complete Guide)

Step 4: Write in Warm, Personal Language

Peer reviews land better when they sound like they came from a real teammate. Use the peer’s first name. Avoid corporate phrasing that would sound stiff in a hallway conversation. A line like “Sam is a delight to work with and has been one of the standout collaborators of my year” often lands harder than three paragraphs of formal evaluation.

Step 5: Read It Back Before Submitting

Read the review aloud, once. Ask yourself two questions. Would you be comfortable if the peer saw exactly these words with your name attached? Would you be comfortable if they saw them without your name? Both answers should be yes.

Common peer review pitfalls to avoid:

Writing something so generic it could apply to anyone on the team. If the sentence would fit ten of your teammates, it is not specific enough.
Being so kind you say nothing useful. A review with only warm praise offers no signal for growth.
Being so honest you say something harsh. Constructive feedback is a gift; personal criticism is a wound.
Delivering surprise feedback. If you have a real concern about a peer, raise it in the moment during the year, and use the review to reinforce or extend the conversation.
Making the review about yourself. Peer reviews are about the peer’s work and behavior, and long personal commentary about your own reactions tends to distract from the signal.
Letting a single recent event dominate the review. A rough final month can overshadow eleven months of strong work if you are not careful to look back across the whole period.
Copying language you would use for a manager review. Peer reviews read best in a more conversational voice, closer to how you would describe a teammate to a friend.

Part 4Common Biases That Distort Peer Feedback

Even careful reviewers carry biases that shape what they notice and how they describe it. Naming these patterns before you write helps you catch them in your own draft.

Recency bias. A strong final month or a rough final week can crowd out the rest of the year in your memory. Look back across the whole period, not just the weeks right before the deadline.
Halo and horn effects. A peer who impresses you in one area, like technical skill, can seem strong in every area by association. The reverse happens too: one visible mistake can color how you read everything else they did.
Similarity or affinity bias. People often rate peers who share their working style, background, or personality more generously than peers who work differently. Ask yourself whether you would describe the same behavior the same way if a very different colleague had done it.
Leniency and central tendency bias. Some reviewers rate everyone positively to avoid discomfort, or rate everyone in the safe middle to avoid standing out. Both patterns erase the signal a 360 is supposed to produce.
Communication style bias. Confident, talkative colleagues often get credit for ideas that more deliberate colleagues raised first or contributed to just as much. Give credit for the substance of the contribution, not only for who spoke loudest in the room.
Contrast bias. Reviewing several peers back to back can make an average performer look weaker simply because they followed a standout, or stronger because they followed someone who struggled. Judge each peer against the expectations of their role, rather than against the last review you wrote.

None of these biases are a character flaw. They are simply how human attention works under time pressure. The fix is a slower first draft and a second read focused specifically on evidence: for every claim you make, ask whether you can point to a real moment that supports it.

Part 5Writing Peer Reviews by Tone

The tone of a peer review should match the pattern of the peer’s year. Below are example phrases across three common tones.

Positive Peer Reviews

Reserved for peers who have been genuinely strong across the review period. The strongest positive peer reviews weave specific moments into the praise so that the words feel earned.

Sarah has been one of the most generous collaborators I have worked with this year. She consistently offers her time and expertise, and she has been my go-to partner for anything analytics-related.
Michael brings a rare combination of technical depth and calm judgment. His code reviews have quietly elevated the standard for our whole team.
Priya has been a stabilizing force during a busy year. During the reorganization in Q2, she was the person on the team who kept the group focused when others were losing sleep.
Diego handled the Q3 client escalation with a level of composure I have tried to learn from. Watching him navigate that conversation shifted the way I approach my own hard calls.
Yuki has been especially strong at pulling people into the conversation. In our cross-team meetings, she consistently names the perspectives that would otherwise go unheard.
James is one of the quiet leaders on our team. He rarely takes credit, and I want to name specifically that his mentorship of our two newest teammates has made a real difference to the group.
Mia consistently delivers work of exceptional quality, and the care she puts into her writing is one of the reasons our team communicates so clearly across functions.
Rob’s partnership on the platform migration was one of the highlights of my year. He carried the harder half of the coordination and made it look easier than it was.

Constructive Peer Reviews

Reserved for growth areas you have noticed across the year. The strongest constructive peer reviews describe behavior rather than character, and offer a specific direction for growth.

One area I would gently name for Sarah is speaking up earlier in leadership meetings. The ideas she surfaces afterward in Slack are almost always the best in the room, and I would love to see her share them live.
Michael occasionally moves quickly to a technical solution before the group has fully agreed on the problem. Slowing down to align on the problem first would make his solutions land even harder.
Priya has grown a lot this year in project management, and the next step for her would be sharing written updates on a more predictable cadence so stakeholders always know where a project stands.
Diego tends to absorb more of the coordination on shared projects than the role really requires. Delegating a bit earlier would free him for the strategic work only he can do.
Yuki writes clear documents and speaks well in small groups. The next area for growth would be presenting to larger audiences with the same clarity, especially in the quarterly reviews.
James has been reliable across every commitment this year. One area I would name is giving feedback more directly to peers in real time, which I know he does quietly but which would carry more weight if it were more visible.
Mia sometimes holds back her opinion on strategic questions, waiting to hear where the group lands first. Her instincts are usually right, and sharing them earlier would help the team.

Balanced Peer Reviews

A balanced peer review names one honest strength and one honest growth area, both grounded in specific evidence.

Jamie has been a reliable partner across every project we have shared this year, and her written communication has raised the bar for the team. The area I would love to see her keep building is stakeholder alignment during the framing stage of new projects, where she has more insight to add than she often shares.
Marcus brings a steady, calm presence to the team and consistently delivers high-quality work on shared projects. The growth area I would surface is speed of response on written updates during busy weeks, where longer gaps can slow the team down.
Elena has been especially strong on the operational side of our work, and her project plans have kept two of our largest initiatives on track. The next area for growth would be strategic framing when we scope new work, where her perspective would be valuable earlier in the conversation.
Terrell delivers dependable, high-quality technical work and is one of the peers I most trust for a second look on a hard problem. The area I would gently name is cross-team relationship building, where investing more time in quieter periods would strengthen the collaborations later.
Nadia is a thoughtful, deliberate contributor, and her presence in our design reviews has consistently improved the outcome. The growth area I would surface is time management under quarter-end pressure, where her strongest work sometimes runs later than the team’s cadence.

A balanced tone works well for the large majority of peer reviews, since most teammates have a genuine strength and a genuine growth area worth naming. When the feedback you have is more serious, involving a pattern of missed commitments or a conflict that affected the team, a formal peer review is often the wrong venue. Raise that concern directly with the peer or their manager, and use the written review to reflect the pattern honestly rather than to introduce it for the first time.

Part 6360 Feedback Questions

The quality of a 360 process depends heavily on the questions asked. Vague, open-ended questions produce vague, open-ended answers. Focused, behavior-anchored questions produce feedback the employee can actually act on.

Below are four sets of questions, tuned to the direction the feedback is flowing.

Questions for Peers Reviewing Peers

Peer-to-peer questions should focus on collaboration, day-to-day work, and the behaviors peers see up close.

What is one specific strength this person brings to the team?
Describe a moment in the past year when working with this person made your own work stronger.
What behavior of this person do you rely on most in shared projects?
What is one area where you would love to see this person continue to grow?
How does this person show up when the work gets hard or the pressure rises?
Where does this person’s work most improve the team?
What would you most want this person to hear from you if they could not see who was writing?
Describe a moment when this person handled a difficult interaction with care.
What kind of feedback would help this person land at the next level?
Is there anything you have wanted to say to this person that you have not yet found the moment for?

Questions for Direct Reports Reviewing a Manager

Upward feedback questions should focus on the manager’s leadership behaviors, the quality of their 1:1s, and the way they support and challenge their team.

What is one thing your manager does especially well as a leader?
Describe a specific moment in the past year when your manager’s support made a real difference to you.
How would you describe the quality of your 1:1 conversations?
How does your manager handle difficult conversations, including those with you?
What is one thing you would love to see your manager start doing?
What is one thing you would love to see your manager stop doing?
How does your manager give feedback, and how could it be even more useful?
Does your manager set clear expectations for your work? Where could that be sharper?
How does your manager advocate for the team in broader company conversations?
What is one thing you wish your manager knew about your experience on the team?

Questions for Managers Reviewing Direct Reports (Within a 360)

Manager-to-report questions inside a 360 focus on the year’s pattern, the strongest and weakest moments, and the direction of continued growth.

What was this person’s most significant contribution during the review period?
Where did you see the strongest growth in this person over the year?
What is one clear strength you would highlight for the calibration group?
What is the most important area of growth for the coming cycle?
How does this person show up in cross-functional work?
How does this person handle feedback and coaching?
What kind of role or project would help this person continue to grow?
Where would this person benefit from additional support from the organization?
How would you rate this person against the expectations for the level?
What is one piece of feedback this person may not have heard clearly yet?

Self-Assessment Questions for a 360

The employee’s own reflection is one of the four directions a 360 gathers, and it deserves the same care as the questions sent to peers. Good self-assessment questions invite honest reflection rather than a highlight reel.

What is the contribution from this period you are most proud of, and why?
Where do you think you grew the most this year, and what helped that growth happen?
What is one area where you know you have room to grow, even before you read anyone else’s feedback?
What feedback have you received this year that you have already started acting on?
What kind of support, coaching, or project would help you grow the most in the coming period?
Where do you expect your self-assessment might differ from how your peers or manager see the same period?

That last question is worth including even though it feels unusual. Employees who can name the gap between their own view and how others might see them are usually the ones who get the most value out of a 360 report when it arrives.

The 7 Steps Of An Effective Action Plan

For more, see “30 Examples: Performance Review Questions (Employee, Peer, Manager).”

Part 7Upward Feedback (Reviewing Your Manager)

Writing feedback about your manager is one of the most delicate pieces of writing in a career. The feedback carries information your manager cannot get anywhere else, and it also carries real risk if the words land the wrong way.

The stakes are highest when the culture is uncertain. In some teams, upward feedback is truly welcomed and treated as a gift. In others, it can shape how your manager sees you for months afterward without either of you naming it directly. Reading the room before writing matters as much as the writing itself.

The structure that lands best in upward feedback is the same three-part pattern used for constructive feedback in any direction. Behavior, impact, suggestion. Name the specific thing your manager does. Explain how it affects you, the team, or the work. When the moment calls for it, offer a specific version of the behavior that would land better.

Example upward feedback that lands well:

Your feedback on my writing this year has helped me grow in a way I did not expect. The pattern of specific, behavior-anchored comments has been especially useful, and I would love more of that same style on my strategic work in the coming year.
You have been generous with the visibility and credit you give the team, and I want to name specifically how much I have appreciated being included in the leadership planning conversations this year.
The weekly 1:1 practice you have built has been one of the most valuable parts of my workweek. The written recap you send afterward has helped me stay focused on the priorities we agreed on together, and I want to name specifically how much I have appreciated that habit.
During periods of high pressure, decisions have sometimes moved faster than the team has been able to process. A short written note explaining the reasoning behind significant changes would help the group stay aligned when the pace picks up.
Cross-functional decisions have sometimes been made without pulling the team into the conversation early. Including the team in the framing stage of shared initiatives would help us prepare and contribute more effectively.
The way you handled the client escalation in Q2 gave me a clear model for how to handle similar moments with my own accounts. Being invited into more of those conversations, even as a listener, would help me continue to build that skill.
Recognition of the team’s work has occasionally been quieter than the effort warranted. Even brief written acknowledgment in the team channel would go a long way for the group’s energy.
The pace of meetings during the busiest quarters has sometimes been difficult to sustain. A monthly meeting audit could help us protect the time we need for focused work.

A useful test before submitting upward feedback: read the sentence aloud and ask whether it would hold up if your manager could see who wrote it. If yes, the language is probably grounded enough to serve the feedback well. If no, either the tone needs softening or the content needs tightening.

Reading Your Culture Before You Write

Not every team is equally ready for direct upward feedback, and part of writing it well is reading the room first.

Look at how your manager has responded to feedback in the past, from you or from others on the team. A manager who has visibly adjusted behavior after hearing something hard is usually safer to be direct with.
Notice whether upward feedback in your organization is anonymous, attributed, or somewhere in between. The format changes how much detail is wise to include.
If you are uncertain how a piece of feedback will land, consider raising the lighter version in writing and saving the harder conversation for a 1:1, where tone and follow-up questions can soften a message that might read as blunt on the page.
If a team has a real pattern of discomfort around upward feedback, that is itself important information. Consider raising concerns through whatever channel feels safest for you, and weigh how much detail to put in writing accordingly.

Part 8360 Templates

Below are two templates you can adapt to your team’s 360 process.

The Questionnaire Template

Used to collect the raw feedback from peers, reports, and the manager. Kept short so respondents actually complete it thoughtfully.

Template

360 Feedback Questionnaire for [employee], [role], [period].

Your relationship to [employee]: [manager / peer / direct report / cross-functional partner].

What is [employee]’s strongest contribution during the review period? Please share one specific example.
What is one area where you would love to see [employee] continue to grow? Please describe the behavior you have observed.
How does [employee] show up when the work gets hard or the pressure rises?
What kind of feedback would help [employee] land at the next level?
Is there anything else you would like [employee] or their manager to know as part of this review?

The Summary Report Template

Used to synthesize the raw responses into a report the employee and their manager can act on.

Template

360 Feedback Summary for [employee], [role], [period].

Summary of feedback sources: This report reflects input from [manager], [number] peers, and [number] direct reports.

Themes from the feedback:

Clearest strengths. Across the responses, the most consistent theme was [strength 1]. A second strong theme was [strength 2].
Common growth areas. The most consistent growth theme was [growth area 1]. A second theme was [growth area 2].
Where perspectives converge. The strongest agreement across the three groups was on [area of alignment].
Where perspectives differ. The most notable difference in perspective was [where views diverge], most often between [group A] and [group B].

Focus areas for the next cycle: Based on the feedback, [employee] and their manager will focus on [two or three specific areas], with support from [coaching, training, or peer mentorship].

The Rating Scale Template

Some 360 processes add a numeric rating alongside the written comments, usually on a three- or five-point scale covering a handful of core competencies. Numeric ratings make it easier to spot patterns across a large group and to track change from one cycle to the next.

Numeric ratings also carry a real cost. They can flatten nuanced feedback into a single digit, and they tend to pull respondents toward the safe middle of the scale when they are unsure how a lower score will be used. Many organizations that use a rating scale keep it narrow, five competencies at most, and require a written comment alongside any score below the top of the scale.

Template

Rate [employee] on each area using the scale: 1 = significant growth needed, 2 = developing, 3 = meets expectations, 4 = strong, 5 = exceptional. A written comment is required for any score of 1 or 2.

Collaboration and teamwork: [1-5], comment: ___
Communication clarity: [1-5], comment: ___
Reliability and follow-through: [1-5], comment: ___
Judgment and decision-making: [1-5], comment: ___
Growth and coachability: [1-5], comment: ___

For more, see “What is 360 Degree Feedback? [Questionnaire Template].”

Part 9Receiving and Acting on 360 Feedback

Writing thoughtful feedback is only half of a 360 process. The other half, receiving it well and turning it into real change, is where most of the long-term value actually gets created.

For the Employee Receiving the Report

A 360 report can be a lot to absorb in one sitting, especially the first time you receive one. A few habits make the experience more useful and less overwhelming.

Read the report once for the overall feeling, then set it aside for a day before reading it again for the details. The first read is often more emotional than analytical, and a second read a day later usually surfaces the patterns more clearly.
Look for repetition across reviewers before reacting to any single comment. One person’s observation is a data point. The same observation from three people in different roles is a pattern worth taking seriously.
Resist the urge to identify who wrote which comment, even when anonymity makes it tempting to guess. Guessing tends to shift your attention toward the relationship and away from the substance of the feedback.
Bring your reaction to the follow-up conversation, including the parts that stung. A manager or coach who only hears that everything makes sense cannot help you work through the parts that felt unfair or surprising.
Pick one or two focus areas rather than trying to address every growth theme at once. A 360 report often names more growth areas than any one person could reasonably work on in a single cycle.

How to Create and Write a Work Plan

For the Manager Delivering the Summary

The way a manager delivers a 360 summary shapes whether the employee leaves the conversation energized or defeated.

Share the strengths first, and give them real weight. Employees remember the growth areas far more vividly than the praise, so the praise needs to be specific and clearly stated to register at all.
Frame growth areas as patterns rather than as a list of complaints. Explaining that three peers independently raised the same theme lands very differently than reading three separate comments aloud.
Leave room for the employee to respond, including pushing back on a piece of feedback that feels off base. A 360 report is a set of perspectives, and an employee’s context can genuinely change how a piece of feedback should be read.
End the conversation with a plan. Agree on one or two focus areas, name what support you will provide, and set a time to check back in.

Part 10Common 360 Review Mistakes

Even well-run 360 programs fall into a familiar set of traps. Watch for these when designing or participating in one.

Tying 360 too tightly to compensation. When 360 feedback directly influences pay, respondents often shift toward safer, kinder answers. The feedback quality drops. Many mature 360 programs keep the compensation link light, using the 360 as an input to development conversations while relying on the manager review for the compensation call.

Lack of anonymity. When respondents feel their words can be identified, they hold back the harder feedback. The strongest 360s protect anonymity carefully, especially for direct reports giving upward feedback, and communicate the anonymity commitment clearly upfront.

Over-aggregation that loses signal. Some 360 reports summarize the responses so heavily that the specific, actionable feedback disappears. Aggregated statements like “peers rated communication as a strength” tell the employee very little. The strongest reports preserve specific comments and quotes wherever anonymity allows.

Skipping the synthesis step. Raw feedback from ten different respondents rarely lands well without a synthesis. Employees who receive an unsynthesized 360 often feel overwhelmed by the volume and unable to see the pattern. The synthesis step, done by the manager or a coach, is what turns raw input into useful development guidance.

Running 360 too often. A full 360 is a significant time investment for many people. Running one every review cycle burns out participants and produces lower-quality feedback over time. Many organizations get the most value by running a full 360 every 18 to 24 months, with lighter peer input in the years between.

Asking questions that are too open. Questions like “What is this person like to work with?” tend to produce vague answers. Focused, behavior-anchored questions produce more useful feedback and cost respondents less time to answer.

Skipping the follow-up. A 360 that ends when the report is delivered often produces little change. The follow-up conversation, ideally between the employee and their manager or coach, is where the feedback becomes a plan.

Not preparing reviewers for how to write useful feedback. Many respondents have never been taught the difference between a vague comment and a specific, actionable one. A short set of instructions or examples included with the questionnaire often improves the quality of every response that follows.

Ignoring the context each group brings. A peer working the same shift sees a different slice of the year than a director working with the employee once a quarter. Reading every comment as equally representative of the whole year, without weighing who actually had the chance to observe what, can produce a distorted picture.

Frequently Asked Questions

How often should we run 360 feedback?

Most organizations get the strongest value by running a full 360 every 18 to 24 months, with lighter peer input during the years between. Running one every cycle usually burns out participants and produces lower-quality feedback over time.

Should 360 feedback be anonymous?

Yes, especially for direct reports giving upward feedback. Anonymity protects the honesty of the feedback and reduces the political risk for participants. Make the anonymity commitment clear upfront, and honor it carefully in the summary report.

Should 360 feedback affect compensation?

The strongest 360 programs keep the compensation link light. When feedback directly influences pay, respondents shift toward safer answers and the quality of the feedback drops. Many organizations use the 360 as input to development conversations while relying on the manager review for compensation decisions.

How many peer reviewers should we include in a 360?

Five to eight peer reviewers usually produces enough signal to identify themes while keeping the workload sustainable. Fewer than three peers risks the feedback being dominated by one voice; more than ten tends to produce diminishing returns for the effort involved.

How do I give feedback about a peer I do not know well?

Skip the review if you do not have enough interaction to offer specific feedback. Vague comments from peers who did not work closely with the person often produce noise that dilutes the signal from those who did. Most 360 tools allow you to decline participation, and a thoughtful decline is more useful than a vague response.

What if the feedback I receive conflicts across the three groups?

Divergent feedback is common and often useful. Peers, managers, and direct reports see different behaviors and often see them from different angles. The most useful step is to look for the pattern within each group first, then explore what might explain the differences. Sometimes the behavior varies by audience. Sometimes one group has access to information the others do not.

How long should a peer review be?

Most strong peer reviews run between 100 and 300 words. The right length is enough to name one specific strength and one honest growth area with a real example. Longer peer reviews tend to lose focus; shorter ones often lack the specificity that makes them useful.

Is it okay to write critical feedback about my manager?

Yes, when the culture supports it and the feedback is grounded in specific behavior with clear impact. Ground every piece of feedback in something you have observed. Offer a suggestion when it fits. Avoid personal characterization. If the culture in your team makes upward feedback dangerous, that itself is useful information worth considering.

What is the difference between a peer review and 360-degree feedback?

A peer review is feedback from one colleague at the same level, usually written as a single piece of input into a broader process. A 360 is the broader process itself, combining peer feedback with self-assessment, manager feedback, and often upward feedback from direct reports into one composite picture.

How do I write a peer review about someone I have had conflict with?

Focus strictly on observable behavior tied to the work, and leave out anything related to the personal friction between you. If the conflict makes it genuinely hard to write anything fair, it is often better to name that limitation to whoever is running the process rather than submit a review shaped by the tension.

Should 360 feedback use a numeric rating scale?

A numeric scale can help spot patterns across a large group, but it works best alongside written comments rather than in place of them. A narrow scale with required comments for any low score tends to produce more useful results than a scale used on its own.

Can peer reviews be used for promotion decisions?

Yes, many organizations include peer input as one piece of evidence in a promotion case, particularly for roles where collaboration and cross-team influence matter. Peer feedback works best as supporting evidence alongside the manager’s assessment and concrete outcomes, rather than as the sole basis for the decision.

What if I am new to a team and do not know my peers well enough to review them?

Say so honestly rather than writing a generic review to fill the space. Most 360 processes allow a respondent to note limited working history, and that note is more useful to the process than a review built on a few weeks of casual observation.

How is a self-assessment different from a peer review?

A self-assessment reflects on your own year in your own voice, including your view of your strengths, your growth areas, and the context behind decisions others may not have seen. A peer review reflects someone else’s observations of you, which makes it a useful check against your own perception rather than a repeat of it.

How do I prepare for a conversation about my own 360 feedback?

Read the report at least once before the conversation so your first reaction happens in private rather than in the room. Note which comments repeat across reviewers, since those patterns matter more than any single comment. Come with a question or two about anything that feels unclear or surprising, since the conversation is a chance to understand the feedback as well as to receive it.

Conclusion

Peer reviews and 360 feedback surface the parts of an employee’s work that no single perspective can capture on its own. Written well, they give the employee a fuller picture of their year and give the manager the depth of signal needed for a fair, thoughtful review.

When you are ready to go deeper, return to our complete guide “Performance Reviews: The Complete Guide” for the full system. For the largest phrase library across every competency, see “2000+ Performance Review Phrases: The Complete List.”

Posted in: Complete Guides