360 Feedback Examples for Your Manager, Peers, Team, and Yourself

You can copy sixty well-written comments into a 360 form and still hand someone a review that tells them nothing.

That sounds unfair, because the comments are the part everyone worries about. They are also the part that gets all the coverage: search for 360 feedback examples and you will find thousands of sample sentences sorted into competencies, which is genuinely useful when you are staring at an empty text box on a Thursday afternoon. What almost nobody shows you is the thing those sentences add up to. A 360 review earns its name because four different groups describe the same person, and the value sits in the places where their descriptions do not match.

So this post does both. It starts with one complete 360 review, a single employee seen by themselves, their manager, their peers, and their direct reports, including the aggregated result and the development plan that came out of it. Then it gives you 60 examples organized by who is writing, because a peer and a direct report are solving very different problems when they sit down to fill in the same form.

What Makes a 360 Comment Usable

A 360 comment is usable when the person reading it can act on it without having to guess what you meant. That comes down to three tests.

Here is the same feedback failing and then passing all three:

Before: "Sometimes hard to work with on tight deadlines."

After: "During the March migration, I asked twice for the updated schema before I got it, and I lost about half a day rebuilding against the old one. Sending the file when the change is made would save the downstream work."

The second version is longer, and that is fine. If you want the question side rather than the answer side, we have a separate bank of 360 feedback questions organized by competency and rater.

A Complete 360 Review, Start to Finish

What follows is an illustrative composite rather than a real customer. The pattern in it, though, is the most common thing a 360 surfaces, and it is worth seeing whole before you look at any phrase bank.

The subject is Arun, a team lead in a support organization. Strong individual contributor for four years, promoted into managing the team fourteen months ago, and now up for a first 360 review. The competency under review is delegation and how they handle disagreement. Six people rated them: their own manager, two peer team leads, and three direct reports.

What Arun said about themselves

What their manager said

What two peers said

Average peer rating on delegation: 3.5 out of 5.

What three direct reports said

Average direct report rating on delegation: 2.3 out of 5.

Where the four views disagree

Read those four sections again and notice what happened. Arun and their manager broadly agree, and they agree in the most flattering direction. The peers are lukewarm. The direct reports, who are the people actually on the receiving end of the delegation being rated, are two full points below the manager.

This is the pattern worth internalising, because a conventional manager-led review would have found none of it. Arun's manager sees outputs, and the outputs are excellent. The team's experience of how those outputs get produced is invisible from that vantage point, and it only becomes visible when you ask the people below rather than the person above.

The specific shape here also has a name in the way people talk about 360s. Arun is what the literature would call an over-estimator, someone whose self-rating sits meaningfully above how their raters see them. The Center for Creative Leadership's guidance on interpreting 360 results treats that gap as one of the more important things in the report, because rating yourself consistently higher than others rate you is associated with a greater risk of derailment later on. It is also the one thing in a 360 that no phrase bank can help you find, since it is not contained in any single comment.

What the aggregated report showed

The interesting rows are not the low ones. Communication scores modestly across the board and everybody roughly agrees, which makes it a straightforward thing to work on. Reliability is uniformly high and needs no attention at all.

The two rows that matter are delegation and handling disagreement, because those are the rows where the disagreement between groups is larger than the disagreement about the score. A 2.0 gap on handling disagreement means Arun and their direct reports are not describing the same behaviour differently. They are describing different experiences of the same events.

The development plan that came out of it

The temptation after a report like this is to write a plan addressing all four rows. That produces a document nobody revisits. One behaviour is enough, as long as it is specific and someone checks.

The commitment: on any decision that changes what a team member is working on, Arun brings the decision to that person while it is still open, states plainly that it is still open, and asks for their view before settling it.

How it gets checked: at the next skip-level conversation in 90 days, Arun's manager asks the three direct reports one question, which is whether they were asked for input before decisions affecting their work were made. Not whether Arun has improved, which invites a polite yes, but whether the specific thing happened.

What success looks like: the direct report rating on handling disagreement moves at the next cycle, and the gap narrows from either direction. If Arun's own self-rating drops while the team's stays flat, that is also progress, because it means the self-awareness arrived even if the behaviour is still catching up.

360 Feedback Examples by Rater Relationship

Most example banks sort by competency. Sorting by who is writing is more useful, because the constraints are completely different. A direct report reviewing their manager is managing a real power imbalance. A peer is describing someone they see sideways and partially. Someone writing about themselves is fighting the urge to either inflate or perform humility.

All 60 examples below are written in second person so you can adapt them directly.

Self-review examples

Self-reviews go wrong in two opposite directions, and both are attempts to control how the review is read. Inflation is the obvious one. The subtler one is strategic modesty, naming a weakness so minor that mentioning it is really a way of claiming there are none.

These 6 name a strength with evidence rather than a verdict.

1. "I rebuilt the onboarding checklist in February after the third handoff miss, and we have not had a repeat since."
2. "I took the two escalations in Q2 personally rather than routing them, which resolved both, and I now think that was the wrong call for the team's development."
3. "I asked for the pricing objection to be added to the team's talk track after hearing it four times in one week."
4. "I have got better at ending meetings early when the decision is made instead of using the full slot."
5. "When the schema change broke two downstream teams, I wrote the postmortem myself rather than waiting to be asked."
6. "I moved my one-to-ones from monthly to fortnightly in March, and I have not cancelled one since."

These 6 name a development area without either inflating or hiding.

7. "I decide quickly and explain afterwards. That works when the decision only affects me and creates rework when it does not."
8. "I have avoided two conversations about underperformance this year, and the delay made both harder than they needed to be."
9. "I still pick up the difficult customer calls myself instead of coaching someone through one, which is comfortable for me and not useful for the team."
10. "I read being protective of the team's focus as a strength. Some of my team may be reading it as being left out of the reasoning."
11. "I am better at written updates than verbal ones, and I have let that mean my team hears less from me during busy weeks."
12. "I have not asked for feedback from my own team in the fourteen months I have been leading it."

If you are writing a fuller self-assessment rather than a 360 section, our bank of self-appraisal comments by competency goes wider.

Peer-to-peer examples

Peers see a partial view, which is a feature rather than a limitation. They see how you behave when nobody senior is watching, and they are the only group who sees you handle a disagreement between equals.

These 8 describe a behaviour worth repeating.

13. "When design and engineering deadlocked on the checkout flow, you got both sides restating the constraint instead of picking a side, and we shipped something both teams stood behind."
14. "Your handover notes on the Fenwick account were the only ones I did not have to follow up on."
15. "You flagged that my timeline assumed a freeze that had already moved. That saved me two weeks of building against the wrong date."
16. "In the incident review you said your team's change had caused it before anyone asked, which set the tone for the whole conversation."
17. "You cover the escalation rota without being asked, including the weekend after the release."
18. "You told me directly that my draft was not ready rather than letting it go to the client. That was the more difficult option and the right one."
19. "You asked the awkward question on the vendor call about renewal terms, and the answer changed our scope."
20. "When I disagreed with your routing proposal you asked me to write up the alternative rather than defending the original."

These 7 name something to change, from a position of no authority.

21. "During peak weeks I lose visibility of what your team has decided. I have twice found out afterwards that a change affected my roadmap."
22. "You decide fast, which mostly works well, and it means decisions touching my team sometimes arrive as finished rather than open."
23. "In the planning session you spoke to about nine of the fifteen minutes. I had two things I did not get to raise."
24. "I have asked twice for the updated schema and got it after the second ask. Sending it when it changes would save the rebuild."
25. "When we disagreed on the migration order, the conversation felt like it was about agreeing with you rather than about the order."
26. "Your status updates tell me what is done and not what is at risk, so I find out about slips late."
27. "You committed my team to the November date in the steering meeting without checking with me first."

For more on the sideways relationship specifically, we have a longer set of peer feedback examples for difficult situations.

Upward feedback examples, direct report on manager

This is the hardest category to write and the thinnest one in most example banks, which is unfortunate, since upward feedback is the part of a 360 most likely to contain something the organization does not already know. Arun's review above turned entirely on it.

The rule that makes upward feedback safe to write is to describe your own experience rather than diagnosing your manager. "You are a micromanager" is a verdict they can dispute. "I checked with you before sending the three emails last week" is something that happened.

These 7 describe something the manager should keep doing.

28. "You said in the December review that the missed target was a resourcing decision you made, not something I got wrong. That changed how safe I felt raising problems after it."
29. "You have not cancelled a one-to-one since March, and knowing the slot is real means I save things for it instead of escalating."
30. "When I brought you the half-formed idea about queue routing, you asked questions instead of fixing it, and I finished it myself."
31. "You told me what you did not know on the reorg rather than filling the gap with reassurance."
32. "You pushed back on the deadline the client asked for rather than passing it to me to absorb."
33. "You gave me the customer call that I was not obviously ready for, and then debriefed it with me afterwards."
34. "You changed your position in the routing discussion after I made the case. That is the reason I bothered making the next one."

These 8 name something to change, which is the set most people need and cannot find.

35. "The decisions that affect my queue have usually been made by the time they reach me. I would like to be asked before, even if the answer is the same."
36. "I do not always know why we are doing something, so when a customer pushes back I end up defending reasoning I do not have."
37. "When I raised a different view on the routing change, the conversation felt like it was about bringing me round rather than about whether I was right."
38. "I have autonomy over the small things and not over the ones that matter to me, and the difference is not written down anywhere."
39. "You go quiet during peak weeks, which is when I am least sure whether my priorities are still the right ones."
40. "I found out about the team restructure from someone outside the team. I would rather hear difficult news from you and early."
41. "You review my work by rewriting it. I would learn more from one round of comments than from the finished version."
42. "In the last three one-to-ones we spent the time on status. I have development questions I have not managed to raise."

Manager-on-employee examples

The manager view is the one most likely to be generous and least likely to be specific, because managers see results rather than process. The discipline here is to write about something you actually observed rather than something you inferred from an outcome.

These 6 are worth repeating.

43. "You ran the launch standups so that engineering, marketing and support all knew their blockers by 9:15, and the launch shipped without a missed handoff."
44. "You told me the number was going to miss three weeks before it missed, which is the reason we had options."
45. "You took the postmortem on the schema break and named your own part in it first."
46. "You coached Priya through the escalation instead of taking it yourself, and she has handled the two since without help."
47. "Your written updates are the ones I forward without editing."
48. "You said no to the regional project on the grounds that your team could not absorb it. I would rather have that than a yes that slips."

These 6 name something to change.

49. "In the vendor pricing call, three people asked you to repeat the figures. Confirming understanding before moving on would prevent that."
50. "Your team's work lands consistently and I hear very little from them directly. I would like them in more of the rooms."
51. "You have taken both escalations personally this quarter. The next one is a development opportunity for someone else."
52. "The Q2 update told me what was complete and not what was at risk, so the November slip reached me late."
53. "You have not put your own name forward for a cross-team project this year, and I have stopped waiting for you to."
54. "You raised the concern about the routing change with me privately after agreeing with it in the room. I would rather have the disagreement in the room."

If the constructive half of this is where you are stuck, our guide to structuring constructive feedback covers the frameworks in more depth.

Cross-functional and client examples

The fifth rater group gets left out of most 360 designs and most example banks. For anyone in a client-facing or matrixed role, it is often the group with the most specific evidence, because they experience the work without any of the internal context that softens it.

55. "Your weekly summary is the only supplier update I do not have to chase, and it is the reason I stopped asking for a call."
56. "You told us the integration would slip before we asked, which meant we could move our own launch rather than explain it afterwards."
57. "In the escalation you stayed on the line until we had a workaround instead of routing us to a ticket."
58. "Your team and your account manager gave us different answers about the migration date in the same week."
59. "We hear from you when something goes wrong and rarely otherwise, so the relationship feels reactive."
60. "You answered the compliance question with a document rather than a conversation, and it took three rounds to establish it did not apply to us."

Ten 360 Comments That Look Fine and Are Not

These are the ones that get submitted most often, because they feel like feedback while committing to nothing.

What to Do When a 360 Lands on You

The first instinct on reading a 360 is to work out who wrote what. It is a completely natural response and it is the fastest way to waste the exercise, because the moment attribution becomes the question, the content stops being the question.

A more useful sequence is to separate the pattern from the outlier. If one person says something and nobody else does, it is one person's experience, and it is real for them without necessarily being a pattern. If three people describe the same thing in different words, you are looking at something structural, and the fact that they used different words is what tells you they were not comparing notes.

Then read for the gap rather than the score. Where do you rate yourself higher than everyone else does, and where lower? The rows where you and your raters agree, high or low, need the least thought. You already know about those. The rows where you disagree are the ones the review was actually for.

The last part is the hardest. A 360 tells you how you are experienced, and how you are experienced is not the same thing as what you intended. Arun genuinely was protecting the team's focus. Their team genuinely was being left out of the reasoning. Both of those are true at once, and the plan only works if the person receiving it can hold both without needing to establish which one was fair.

Making 360 Feedback Honest Enough to Be Worth Reading

None of the sixty examples above matter if the person writing does not believe it is safe to submit them.

That is worth sitting with, because it is a structural condition rather than a matter of encouragement. Look again at the upward feedback section. Every one of those comments carries some risk for the person writing it, and the eight in the second half carry considerably more. A direct report deciding how honest to be about their manager is making a calculation about their own position, and no amount of framing in the invitation email changes the arithmetic. What changes it is whether the responses are genuinely anonymous, whether the rater group is large enough that a single comment cannot be traced by elimination, and whether anything visible happened the last time people told the truth.

That last condition is the one organizations skip. Feedback programmes rarely die because the questions were wrong. They die because a cycle ran, nothing changed, and the next invitation arrived anyway. Collecting anonymous feedback and then being able to respond to it without breaking anonymity is what keeps the loop alive, which is the part of the problem Vantage Pulse is built for: anonymous responses, sentiment across categories, and a two-way conversation thread so a comment can be followed up without anyone having to identify themselves.

For the mechanics of designing and running the cycle itself, our guide to the 360 degree feedback process and best practices covers rater selection, timing and follow-up.

Conclusion

Good 360 comments are worth writing, and the sixty above will save you the blank-page problem. But the reason to run a 360 rather than a conventional review is not that it produces better sentences. It is that it produces disagreement, and disagreement is information.

Arun's manager and Arun both thought delegation was a strength. Three people who reported to Arun thought it was the weakest thing about working for them. Neither view was dishonest and neither was complete. A review with one rater would have recorded the flattering half and filed it, and the plan that came out of the process only existed because somebody asked the other five.

So when the report arrives, resist the urge to average it. Look for the rows where the groups do not match, pick the one that matters most, change one behaviour, and have someone check in ninety days whether the people who raised it noticed anything different.

Frequently Asked Questions

1. Why do my self-ratings differ from what my team said?

Because you are rating your intentions and they are rating their experience of the results, and those two things come apart most often around delegation and disagreement. In the review above, the team lead rated their own delegation at 4 and their three team members averaged 2.3, and neither number was dishonest. A gap in that direction, where you sit above your raters, is the one worth taking seriously, because it means the behaviour you believe you are demonstrating is not reaching the people it is aimed at.

2. Should 360 comments be written to the person or about them?

Write to them, in second person, if the platform shows comments to the subject as submitted. "You ran the standups so everyone knew their blockers by 9:15" reads as feedback, while "John ran the standups well" reads as evidence being filed about someone. Third person is only right when a facilitator is going to summarize and paraphrase before the subject ever sees it, which is worth checking before you start writing.

3. What do you write for someone you barely work with?

Say that, and say it plainly, rather than producing something vague to fill the box. A comment that reads "I have worked with you on two projects this year and cannot speak to how you handle disagreement" is genuinely useful, because it tells whoever reads the report to weight your ratings accordingly. Vague praise from a distant rater is worse than an honest gap, since it dilutes the average without adding any information.

4. How specific can a comment be before it identifies you?

Name the behaviour and the effect, but leave out the details only one person could know. Referring to a decision that changed your own work is usually safe in a rater group of three or more. Referring to a conversation that happened in a one-to-one only you attended is not, no matter how the survey is labelled. If a comment could only have come from you, treat it as signed regardless of what the tool promises.

5. What happens after the 360 report arrives?

Someone reads it with the subject, they pick one behaviour, and a date gets set to check whether it changed. That is the whole of it, and skipping the last part is why most 360 programmes quietly stop working. A plan addressing four competencies at once is a document nobody revisits, while one specific commitment with a named check in ninety days is something a person can actually be held to.

6. Should 360 feedback be tied to pay or promotion?

Generally no, and the reason is visible in the examples above. The moment ratings affect someone's compensation, raters start managing the consequences rather than describing the behaviour, peers have an incentive to score each other down, and direct reports have a strong incentive to score their manager up. Keep 360s for development, run them on a separate cycle from compensation decisions, and use the manager's own assessment where a formal rating is required.