360 feedback examples: what strong feedback looks like

A strong 360 feedback example names one observable moment and its effect. A weak one is a label that could apply to anyone. “Great communicator” is a weak example. “In the last planning review she laid out the tradeoffs so clearly the team stopped relitigating the decision” is a strong one. That gap is the whole subject of this article.

Most “360 feedback examples” you will find online are lists of 50 interchangeable phrases, grouped by competency, that you could paste onto any person in your company without changing a word. That’s exactly the problem. The phrases are generic by design, and generic is the thing the person reading their 360-degree feedback report was hoping to escape. So the examples below come in pairs, weak next to strong, with a line on why the strong one works, because the point is to copy the shape, not the words. If you want the deeper reason feedback comes back vague in the first place, why 360 feedback is always vague covers it. This piece is about what the good version actually reads like.

Key Takeaways

• A strong 360 example names an observable moment and its effect. A weak one is a label (“great communicator”) that could apply to anyone. The test: could the person picture the exact situation?
• Positive feedback fails the same way criticism does, by staying generic. “Really collaborative” helps no one; the specific version tells them what to keep doing.
• The move that makes a weakness receivable is describing a behaviour and its consequence, pointing forward, and dropping the character label. “Disorganised” becomes “the spec was not written down before kickoff, so handoffs slipped.”
• Calibrate examples to the rater relationship. Peers describe collaboration in the moment; direct reports describe what a manager protects them from; managers describe patterns over time.
• Do not paste these. Use the pattern (moment, effect, one change), and you can write feedback for situations no list covers.

What separates a useful example from a useless one

There is one test that sorts every 360 comment into useful or useless: could the person picture the exact situation you are describing? If yes, it is specific. If the sentence could be true of half the company, it is a label, and labels do not help anyone change.

Take the most common line in any feedback report: “good communicator.” It commits to nothing. Now the specific version: “she walks the team through the tradeoffs before a decision, so people actually buy in, but she goes quiet when a plan is falling apart and we hear about it late.” That names real moments, and by naming them it becomes useful. The person knows what to keep doing and what to watch.

That’s the pattern behind every example below: a moment, its effect, and for a development point, the one change that would help. Everything else is variation on that.

360 feedback examples for peers

Peers see collaboration in the moment, the informal version of someone that managers rarely witness. So peer feedback should target day-to-day working behaviour, not a verdict on character. Two examples.

Collaboration, as a strength.

• Weak: “Great team player, easy to work with.”
• Strong: “When our projects overlap, they flag the dependency in writing before it becomes my problem, so I have never once been blindsided by their timeline.”
• Why it works: it points at a specific habit and the exact benefit the rater gets from it. The person now knows the thing worth protecting.

Communication, as a development area.

• Weak: “Could communicate a bit better sometimes.”
• Strong: “Decisions on our shared project tend to get made in side conversations I am not in, so I usually find out a plan changed after I have already built against the old one.”
• Why it works: no character judgment, just a pattern and its cost. It’s hard to argue with and easy to act on.

A quick note on positive examples, since people undervalue them: a vague compliment is a wasted opportunity, not a kindness. “You are great to work with” feels nice and teaches nothing. The specific version tells the person which behaviour to keep doing under pressure, which is the entire point of telling them at all.

360 feedback examples for managers (upward feedback)

Feedback about a manager, written by their direct reports, is the highest-stakes and most useful part of most 360s, which is why it needs to be anonymous to be honest. The trap is that reports either say nothing real or render a verdict (“good manager”, “bad manager”). Push for the specific situation instead.

Support, as a strength.

• Weak: “Supportive manager, really cares about the team.”
• Strong: “They hand me the ambiguous problems and let me come back with an approach, then poke holes in it rather than taking it over. That is how I have gotten better at scoping work.”
• Why it works: it describes what the manager actually does and the growth it produced, which is far more useful than “supportive.”

Listening, as a development area.

• Weak: “Should listen to the team more.”
• Strong: “In the last two planning sessions I raised the staffing risk and we moved on without addressing it. I cannot tell whether it was heard and set aside on purpose or just missed, and that uncertainty is what makes me stop raising things.”
• Why it works: it names specific moments, the effect on the rater’s behaviour, and stops short of accusing the manager of not caring. That is a message a manager can receive without getting defensive.

If you are the one running upward feedback and worried about whether people will be honest, the anonymity decision is the thing to get right first, because in a small team “anonymous” is often a polite fiction and reports can usually guess who wrote what.

360 feedback examples for a direct report

When a manager writes feedback about someone on their team, they have the advantage of patterns over time, things a peer only glimpses. Use it. The best manager-to-report examples reference a trajectory or a repeated pattern, not a single incident.

Ownership, as a strength.

• Weak: “Takes real ownership of their work.”
• Strong: “When the Friday deploy broke, they stayed to trace it, wrote up what happened, and changed the checklist so the same failure cannot recur. Nobody asked them to do the last part.”
• Why it works: it is a scene with a beginning and an end, and the detail (the checklist) shows the specific behaviour worth naming.

Proactivity, as a development area.

• Weak: “Needs to be more proactive and take more initiative.”
• Strong: “Your execution is excellent once a task is defined. The next level for you is defining the task yourself, spotting the thing that needs doing before it lands on your plate. The doc cleanup last month is a good example of what I mean; you noticed it, but waited to be asked.”
• Why it works: it separates what is already strong from the one specific thing to grow, and anchors the growth point to a real moment so it is not an abstract instruction.

Imagine a manager preparing for a development conversation who writes “needs to be more proactive” and stops there. In the meeting, the report nods, agrees, and leaves with nothing to actually do, because “be more proactive” is a mood, not an action. The version above gives them a concrete next move. That difference, a comment the person can act on versus one they can only feel bad about, is what the delivery conversation lives or dies on. If that conversation is the part you are unsure about, how to deliver 360 feedback results without breaking trust is the companion to this piece.

360 feedback examples for senior leaders

Feedback for a founder or senior leader tends to come back the vaguest of all, partly out of caution and partly because their work is abstract. Anchor it to decisions and their downstream effects, which are the observable part of leadership.

Clarity of direction, as a strength.

• Weak: “Strong leader with a clear vision.”
• Strong: “In the last all-hands they named the two things we are explicitly not doing this quarter, which made it obvious what to say no to when new requests came in.”
• Why it works: it turns “clear vision” into a specific act with a specific effect on how the team makes decisions.

Consistency, as a development area.

• Weak: “Can be a bit inconsistent with priorities.”
• Strong: “The priority I heard in January was growth. By March it was retention, and the switch was never named out loud, so part of the team spent weeks still optimising for the old goal.”
• Why it works: it shows the cost of the inconsistency (wasted work) without questioning the leader’s judgment, which keeps it developmental instead of adversarial.

Turning a weakness into a strengths and weaknesses example that lands

The reason most weakness feedback fails is that it reaches for a character label, and character labels put people on the defensive before they can hear anything. The fix is mechanical: name the behaviour, name the consequence, name the one change, and delete the adjective about who the person is.

• Weak: “She is disorganised.”
• Strong: “Twice last quarter, handoffs slipped because the spec was not written down before kickoff. Writing a one-paragraph brief first would fix it.”
• Why it works: “disorganised” is a verdict on her as a person, which she will argue with. The specific version is a pattern with an obvious remedy, which she can just fix.

The same move works for every hard piece of feedback. “Arrogant” becomes “in design reviews, pushback tends to get dismissed before it is fully heard, which is why fewer people raise concerns now.” “Not strategic” becomes “the plans are strong on the next two weeks and thin on the next two quarters.” In every case you are trading a label the person cannot use for a behaviour they can. That is also why a rating on its own never does this job: a number is the most generic label of all. The written examples are where the real signal lives, which is how we built written feedback and criteria ratings together in Lynxify.me, with the words kept next to the score rather than replaced by it.

Self-evaluation examples

The self-assessment is the most-skipped and most-revealing part of a 360, because the gap between how someone rates themselves and how their team rates them is where the useful conversation usually lives. Strong self-evaluation is not self-praise or self-flagellation; it anchors to a past moment and a change.

• Weak: “I am a strong communicator and a good team player.”
• Strong: “I disagreed with the Q1 roadmap call and pushed back hard in the meeting. Looking back, the decision was right, and I would raise concerns earlier and with less heat next time.”
• Why it works: it revisits a specific moment and names what the person would do differently, which is genuine reflection rather than a performance of humility.

How to write your own (do not paste these)

Here’s the honest limit of any list of 360 feedback examples, including this one: the examples that matter are the ones about your actual colleagues, and those are not on any page. What you can take from a list is the pattern, not the sentences. Every strong example above is the same shape: a moment you observed, the effect it had, and for a growth point, the one change that would help.

Which means the real work happens upstream, in what you ask and when you ask it. Feedback comes back in the shape of the question, so if you want specific answers you have to ask for a moment, not a rating; 360 feedback questions that surface blind spots covers the question design that pulls these examples out of people instead of getting “good communicator” back. If you want a ready-made starting set calibrated to who you are reviewing, you can generate an anchored set for the role and adapt it. And if you are assembling a full round rather than a single comment, a copy-paste 360 review template for startups gives you the questionnaire, kickoff email, and debrief structure to drop the examples into.

Picture a People Ops lead who collects a batch of responses that all come back generic, “great communicator, really collaborative, could be more proactive.” Rather than pass that on, she goes back to two raters and asks a single follow-up: “can you give me the specific moment you were thinking of?” Both produce a real scene in a sentence. That five-minute move is the difference between a report that changes something and one that gets nodded at and filed. You can do that by hand, or let the synthesis keep the examples attached for you; either way, the rule matters more than the tool.

The example is only as good as the moment behind it

Good 360 feedback isn’t a matter of finding better words. It’s a matter of pointing at something real, an actual moment, its actual effect, and the one thing worth changing, and then resisting the urge to smooth it back into a label. Every example in this guide is just that pattern applied to a different competency and a different rater. Learn the pattern and you will never need a list again, because you will be able to write the specific, slightly uncomfortable, genuinely useful sentence for any situation in front of you.

When you are ready to run a round where the specifics survive instead of getting flattened into themes, you can start your first 360 in Lynxify.me, no annual contract, no credit card required. Or run it with a shared document and the pattern above. The version you actually run beats the perfect one you keep planning.

Frequently asked questions

What is a good example of positive 360 feedback?

A good positive example names one observable moment and its effect, not a trait. Weak: “great communicator.” Strong: “in the last planning review she laid out the tradeoffs so clearly the team stopped relitigating the decision.” The test is whether the person could picture the exact situation and know what to keep doing. If the sentence could apply to anyone, it is not specific enough yet.

What are examples of constructive or weakness feedback in a 360?

Constructive feedback describes a behaviour and its consequence, points forward, and avoids character labels. Weak: “she is disorganised.” Strong: “twice last quarter, handoffs slipped because the spec was not written down before kickoff. A one-paragraph brief first would fix it.” Name the situation, name the effect, name the change. That is receivable in a way that “disorganised” never is.

How do you give a coworker feedback for a 360 review?

Anchor every point to something you personally saw in your day-to-day work, not to a general impression. For a peer, target collaboration in the moment: what they do that you would want copied, or where a handoff breaks down and what the early signal is. Describe the scene and its impact, then, for a development point, name the one change that would help. Keep it about the work, not the person.

What is the most common criticism of 360 feedback?

That it comes back vague and gets used as a verdict rather than for development. Both are fixable. Vagueness is mostly a safety and effort problem, not a wording problem, and it goes away when the specific answer is safe and easy to give. The verdict problem goes away when you keep the 360 developmental and decoupled from pay. The examples in this guide are what feedback looks like once those two things are handled.

What should you never write in 360 feedback?

Character judgments (“lazy”, “arrogant”, “not a team player”), comparisons to other people, and anything you cannot tie to a specific situation you observed. These produce defensiveness and no path to change. Replace the label with the behaviour and the moment that made you reach for it, and the same point becomes something the person can actually act on.