By the 360Feedbacks team · Updated
How to Write Useful 360 Feedback
Good 360 comments describe a situation, the behavior you observed, and its impact (often called the SBI model). They are specific enough to act on and focused on behavior, not personality. Compare:
| Vague | Useful |
|---|---|
| “Great communicator.” | “In project kickoffs, you explain the goal and the deadline before the details, so everyone knows what matters most.” |
| “Needs to be more open.” | “When plans change, I usually hear it from others first. A short message to the team would avoid rework.” |
| “Bad at conflict.” | “Disagreements between teams sometimes get postponed. Naming the issue and setting a time to resolve it would help.” |
Keep comments anonymous in practice
Avoid details only you would know (“as I told you in our Tuesday call”). In a 360, comments are shown without names, but a very specific reference can still reveal who wrote it.
360 Feedback Examples by Competency
Adapt these to what you actually observed. Each competency has two positive and two constructive examples.
Communication
Positive
- “In project kickoffs, you explain the goal and the deadline before the details. Everyone leaves knowing what matters most.”
- “Your written updates are short and easy to act on. I rarely have to ask a follow-up question.”
Constructive
- “In team meetings, decisions sometimes aren’t summarized at the end, so people leave with different takeaways. A two-minute recap would help.”
- “When priorities change, I usually hear about it from others first. A quick message to the team when plans shift would avoid rework.”
Leadership and direction
Positive
- “You connect our weekly work to the company goals, which makes it easier to say no to low-priority requests.”
- “When the client escalation happened, you stayed calm, split the work, and checked in daily. The team followed your lead.”
Constructive
- “Our quarterly priorities are clear to you but not always to the team. Sharing the “why” behind them would help us make better calls on our own.”
- “You often step in to solve problems yourself. Letting the team try first, with you as backup, would help us grow faster.”
Coaching and developing others
Positive
- “Our 1:1s always include something about my development, not just status updates. It shows you care about my growth.”
- “You gave me the vendor negotiation as a stretch assignment and prepared me for it. It was the most useful thing I did this year.”
Constructive
- “I’d like more specific feedback after presentations — what to keep doing and one thing to change.”
- “Development conversations happen mostly at review time. A short check-in every month would make them more useful.”
Giving feedback
Positive
- “Your feedback is specific and timely. After the demo, you told me exactly which slide confused the client and why.”
- “You recognize good work in public and raise problems in private. That makes it easy to hear hard feedback from you.”
Constructive
- “Sometimes I only learn something wasn’t right when it shows up in my review. Hearing it earlier would let me fix it sooner.”
- “Positive feedback tends to be general (“great job”). Saying what specifically worked would help me repeat it.”
Teamwork and collaboration
Positive
- “You share credit generously. In the launch retro, you named each person’s contribution.”
- “When our team was short-staffed, you offered help before being asked.”
Constructive
- “Cross-team requests from your area often arrive at the last minute. Earlier notice would help us plan.”
- “In group discussions, you sometimes move to a decision before quieter team members have spoken. Asking for their view would strengthen the outcome.”
Accountability and results
Positive
- “When you commit to a deadline, it happens. That reliability makes planning much easier for the rest of us.”
- “You own mistakes openly. When the report had an error, you flagged it and fixed it the same day.”
Constructive
- “Some tasks stall without an update. A quick “this will slip, here’s why” message would help others adjust.”
- “You take on many extra tasks, and a few important ones end up late. Pushing back on lower-priority requests could protect your key work.”
Decision making
Positive
- “You make decisions quickly when the data is clear and explain your reasoning, so we can move without waiting.”
- “You involve the right people in big decisions without turning every choice into a meeting.”
Constructive
- “On complex decisions, the reasoning isn’t always shared, so the team sometimes reverses course without knowing why.”
- “Some decisions wait until all information is available. Setting a “decide by” date would keep work moving.”
Conflict management
Positive
- “When two of us disagreed on the rollout plan, you listened to both sides and helped us agree on criteria instead of opinions.”
- “You address tension early, before it affects the work.”
Constructive
- “Disagreements between teams sometimes get postponed. Naming the issue and setting a time to resolve it would help.”
- “In heated discussions, you occasionally answer before the other person finishes. Letting people finish would lower the temperature.”
Adaptability
Positive
- “When the budget was cut mid-quarter, you re-planned quickly and explained the trade-offs clearly.”
- “You are open to new tools and ideas from the team and try them before deciding.”
Constructive
- “When plans change, you adapt quickly, but the team needs a bit more time. Explaining what changes and what stays the same would help.”
- “New processes are sometimes dropped after a few weeks. Giving them a defined trial period would show whether they work.”
Emotional intelligence
Positive
- “You notice when someone is overloaded and adjust assignments without making a big deal of it.”
- “You stay composed under pressure, which keeps the team calm during busy periods.”
Constructive
- “When you’re stressed, your messages get very short and can read as frustration. A quick line of context would help.”
- “You’re very supportive one-on-one; in group settings, acknowledging the team’s effort more often would have the same effect.”
Examples by Rater Type
From a direct report (upward feedback)
- “Our 1:1s always include something about my development, not just status. Please keep that.”
- “I’d find it easier to prioritize if you shared why a project moved up the list.”
From a peer
- “You’re the first person I go to when I need a quick, honest read on a draft.”
- “Requests from your team often arrive late in the sprint; earlier notice would help us plan.”
From a manager
- “You consistently deliver what you commit to, and clients mention your follow-through.”
- “Next step: delegate more of the day-to-day so you have time for the hiring plan.”
Self-assessment
- “My strongest area this year was execution: I hit all four project deadlines.”
- “I need to give feedback more often; I tend to save it for formal reviews.”
Collect Comments Like These — Anonymously
360Feedbacks sends the survey, collects anonymous comments, and groups them by theme in the report. Your first evaluation is free.
Start Your Free 360 →Frequently Asked Questions
What is an example of good 360 feedback?
Good 360 feedback names a situation, the behavior, and its impact: “In project kickoffs, you explain the goal and deadline first, so everyone knows what matters most.” It is specific, observable, and actionable.
How do you write constructive 360 feedback?
Describe what happened and its effect, then suggest one change: “Decisions sometimes aren’t summarized at the end of meetings, so people leave with different takeaways. A two-minute recap would help.” Avoid labels like “disorganized.”
How long should a 360 feedback comment be?
One to three sentences is usually enough. Longer comments are fine if they stay specific; very short ones (“great job”) give the person nothing to act on.
Should 360 comments be anonymous?
Yes. Anonymity makes honest comments more likely. Tools like 360Feedbacks show comments without names and hide group results when fewer than 3 people in a group responded.
Related Guides
New to 360s? Start with what 360 degree feedback is and how it works.