360 Degree Feedback Examples: 100 Ready-to-Use Phrases

Effective 360-degree feedback describes observable behavior, explains its impact, and gives the employee a practical next step. It should not guess at personality, motivation, or intent.

The 100 phrases below are organized into ten competency areas. Each section includes five strength examples and five development examples. Adapt every phrase with a real project, meeting, date, work sample, or outcome from the review period.

This page is a phrase library. For software-selection guidance, use the 360 feedback software buyer guide. For turning feedback into action, use the 360 feedback to IDP guide. To run the full cycle from rater selection through the questionnaire itself, use PerformSpark's free 360 feedback questionnaire template.

How to Write Useful 360 Feedback

Use this structure:

1. Behavior: What the reviewer directly observed
2. Context: Where or when it occurred
3. Impact: How it affected the work or other people
4. Next step: What the employee should continue or change

Keep comments job-related and relevant to the rater's working relationship. A peer may be well placed to comment on collaboration, while a direct report may have better evidence about delegation or coaching. The 360 review workflow should make the purpose, visibility, and confidentiality rules clear before responses are collected.

Communication Feedback Examples

Strengths

1. Explains complex information in language that fits the audience.
2. Provides project updates with clear status, risks, owners, and next actions.
3. Asks clarifying questions before beginning work when requirements are unclear.
4. Listens without interrupting and confirms the main point before responding.
5. Adjusts the level of detail appropriately for leadership, peers, and technical partners.

Development areas

6. Updates would be more useful if they ended with the decision or action required.
7. Important risks are sometimes communicated after stakeholders have limited time to respond.
8. Meeting explanations occasionally include more background than the audience needs.
9. Follow-up messages do not always confirm the owner and due date.
10. Questions and concerns raised by others would benefit from a clearer acknowledgment before the response.

Leadership and People Management Feedback Examples

Strengths

11. Clarifies team priorities and explains why the work matters.
12. Delegates responsibility while remaining available for appropriate support.
13. Provides specific feedback tied to observed work rather than general impressions.
14. Creates space for employees to raise risks and ask for help.
15. Recognizes employee contributions and gives credit to the people who completed the work.

Development areas

16. Decision authority is not always clear when work is delegated.
17. Feedback conversations would be stronger with more specific examples and agreed actions.
18. Team members sometimes receive priority changes without enough context.
19. Development discussions need more consistent follow-through between formal reviews.
20. Workload concerns would benefit from earlier review and clearer tradeoff decisions.

Collaboration Feedback Examples

Strengths

21. Identifies cross-team dependencies before they affect delivery.
22. Shares relevant information with partner teams without waiting to be asked.
23. Handles disagreement by returning the discussion to shared outcomes and evidence.
24. Follows through on commitments made to colleagues.
25. Invites input from people whose work will be affected by the decision.

Development areas

26. Partner teams are not always informed when a decision changes their work.
27. Cross-functional meetings would benefit from more proactive contributions.
28. Dependencies are sometimes treated as another team's responsibility rather than shared work.
29. Responses to partner questions need a more predictable timeframe.
30. Disagreements should be discussed directly before they are escalated.

Problem-Solving Feedback Examples

Strengths

31. Separates the immediate symptom from the underlying cause.
32. Brings possible responses and tradeoffs when raising a problem.
33. Tests important assumptions before recommending a solution.
34. Uses available evidence rather than relying only on first impressions.
35. Documents lessons from significant problems so the team can respond more effectively next time.

Development areas

36. Issues are sometimes escalated without enough initial diagnosis.
37. A preferred solution may be selected before the problem is fully defined.
38. Recurring issues need a more structured root-cause review.
39. Risk communication should occur earlier in the problem-solving process.
40. Resolved issues would provide more value if the approach and learning were documented.

Adaptability Feedback Examples

Strengths

41. Adjusts priorities constructively when business needs change.
42. Learns new tools and processes with limited supervision.
43. Uses feedback to revise work while the change can still affect the outcome.
44. Maintains clear communication during uncertain or changing work.
45. Recognizes when an existing approach no longer fits the situation.

Development areas

46. Changes in direction sometimes result in a longer transition than the work allows.
47. Concerns about a change should be paired with a practical alternative.
48. Feedback needs to be incorporated earlier rather than near final delivery.
49. New-tool adoption would benefit from a defined learning and practice plan.
50. Development activity is often reactive instead of connected to expected future work.

Accountability Feedback Examples

Strengths

51. Communicates early when a commitment is at risk.
52. Owns mistakes and helps define the corrective action.
53. Records decisions and follows up on assigned actions.
54. Keeps shared work status current enough for others to plan.
55. Raises constraints instead of allowing them to remain hidden until a deadline.

Development areas

56. Some commitments are missed without sufficient advance notice.
57. Action items from 1-on-1 check-ins need more consistent follow-through.
58. Project status in shared systems is not always current.
59. Retrospectives should distinguish external factors from actions within the employee's control.
60. Repeated issues need a documented prevention step rather than only a correction.

Technical and Role Expertise Feedback Examples

Strengths

61. Produces work that meets the role's documented quality standard.
62. Explains technical decisions so colleagues can understand the reasoning.
63. Shares useful knowledge through documentation, review, or coaching.
64. Identifies relevant risks before implementation or delivery.
65. Applies new knowledge to actual work rather than treating learning as a separate activity.

Development areas

66. Work would benefit from a more consistent quality check before submission.
67. Technical decisions are not always documented for future users.
68. Peer review participation needs a more reliable cadence.
69. Solutions sometimes prioritize speed without enough investigation of repeat risk.
70. The development plan should include practice opportunities, not only formal learning.

Emotional Intelligence Feedback Examples

Strengths

71. Remains constructive during high-pressure discussions.
72. Shows curiosity about another person's perspective before responding.
73. Delivers difficult feedback with respect and sufficient context.
74. Recognizes when a conversation needs more time or a different setting.
75. Adapts tone and pacing to the situation without avoiding the main issue.

Development areas

76. Critical feedback sometimes receives an immediate defensive response.
77. Direct communication can occasionally sound more personal than intended.
78. Urgent requests need clearer explanation of why the work is urgent.
79. Remote conversations would benefit from more deliberate checks for understanding.
80. Disagreement should remain focused on the work rather than the other person's approach or character.

Initiative Feedback Examples

Strengths

81. Identifies useful improvements beyond assigned tasks.
82. Raises emerging risks before they create a visible problem.
83. Steps into unclear ownership while confirming authority and priorities.
84. Brings relevant external learning into team discussions.
85. Turns an informal observation into a proposal that others can evaluate.

Development areas

86. Risks are sometimes identified but not raised until impact occurs.
87. Team discussions would benefit from more proactive recommendations.
88. Improvement ideas need clearer evidence, scope, and proposed ownership.
89. New responsibilities should be confirmed before work begins to avoid duplicated effort.
90. Development goals need defined actions and review dates through an individual development plan.

Results and Execution Feedback Examples

Strengths

91. Connects completed work to the outcome it was intended to support.
92. Uses clear goals and progress evidence to keep work visible.
93. Maintains quality while responding to a demanding workload.
94. Identifies dependencies early enough to protect delivery.
95. Reviews completed work and applies the learning to the next cycle.

Development areas

96. Output volume sometimes receives more attention than quality or rework.
97. Some goals lack a clear measure or definition of completion.
98. Milestone progress needs more frequent communication between formal reviews.
99. Initial commitments should reflect realistic capacity and dependencies.
100. Strong individual results should be connected more clearly to team outcomes and shared priorities.

How to Adapt the Phrases

Replace general wording with:

• The specific project, meeting, customer, or work cycle
• The behavior the rater directly observed
• The impact on the work or people involved
• The next action or practice expected

Generic: “Communicates risks early.”

Adapted: “During the implementation project, Jordan identified the data-migration risk before testing began, documented the likely impact, and proposed two response options for the project lead.”

How Managers Should Use 360 Feedback

360 feedback should be considered alongside goals, work outcomes, manager observations, and other relevant records. It may provide additional context during performance reviews and calibration, but it should not automatically determine the final rating.

Look for patterns across people with relevant observation. Do not treat one comment, a popular opinion, or a numerical average as the complete assessment. When a theme becomes a development priority, move it into a focused plan with practice, support, milestones, and follow-up.

Common 360 Feedback Mistakes

• Describing personality instead of behavior
• Using invented dates, metrics, or outcomes
• Commenting on work the rater did not observe
• Writing only praise or only criticism
• Providing a gap without a practical next step
• Promising anonymity the process cannot protect
• Using feedback as an automatic rating or compensation decision
• Sending a report without a debrief

Connect Feedback to Development

PerformSpark connects feedback with reviews, surveys, goals, check-ins, calibration, development plans, and reporting.

Explore PerformSpark pricing or book a personalized demo to see how multi-rater feedback can remain connected to the employee's ongoing performance record.