360 Feedback

A 360 collects feedback on one person from their manager, peers and direct reports. The score is not the point — the gap between how you rate yourself and how they rate you is. This covers the questions worth asking, what usable feedback looks like, and how to turn a report into a change.

What 360 feedback actually is

A 360 gathers structured feedback on one person from the people around them: their manager, their peers, their direct reports, and usually themselves. The value is not the score. It is the gap between how someone rates their own behaviour and how the people who work with them rate the same behaviour.

That gap runs in both directions, and both are informative. Leaders who rate themselves harshly are frequently better regarded than they expect. Leaders who rate themselves highly on listening are the ones whose teams most often disagree.

360 feedback versus a performance review

The most common way organisations ruin a 360 is by attaching it to compensation. The moment feedback affects someone's bonus, contributors write strategically and the instrument stops measuring anything.

360 feedback questions that produce usable answers

Rating scales alone give you a number without a reason. Pair each dimension with one open question. These are the ones that consistently produce something actionable:

• What should this person keep doing, because it works and they may not know it?
• What is one thing they do that makes your job harder?
• When did you last see them change their mind? What happened?
• If they were promoted tomorrow, what would worry you?
• What do they avoid?
• Is there anything you would say to them directly that you have not?

The last one is the highest-yield question in most 360s, and the one most templates leave out.

What good 360 feedback examples look like

Useful feedback is behavioural and situational. "Poor communicator" is not usable. "In the Tuesday leadership meeting, she presents conclusions without the reasoning, so people agree without understanding" is. When you brief contributors, ask for the second kind explicitly and give an example, or you will receive adjectives.

Sample themes from a real report read closer to: consistently makes space for junior voices, but reverses decisions after the meeting, which makes people reluctant to commit in the room. That is one sentence someone can act on.

Using 360 feedback for leadership development

1. Run it before the development work, not after. The report is the baseline, not the verdict.
2. Pick one theme. Reports typically surface five or six. Working on all of them changes none of them.
3. Tell the contributors what you chose. This single step does more for perception than the change itself, because people notice what they are looking for.
4. Re-run it in nine to twelve months. Sooner and you are measuring novelty; later and the memory has faded.

A 360 is the strongest instrument available for the blind-spot problem, but it produces a document, not a change. What moves is the conversation afterwards, which is why 360s are usually run inside a coaching engagement rather than on their own. The Johari Window is the standard model for the blind spots it surfaces, and the leadership self-assessment gives you the self-rating half in about three minutes.

Frequently asked questions

What is 360 feedback?

360 feedback is structured feedback on one person collected from the people around them: manager, peers, direct reports and themselves. It is used for development rather than evaluation, and its value lies in the gap between self-rating and how others rate the same behaviour, which is where blind spots show up.

What questions should be in a 360 feedback survey?

Pair each rating dimension with one open question. The most productive are: what should this person keep doing, what do they do that makes your job harder, when did they last change their mind, what would worry you if they were promoted, what do they avoid, and is there anything you would say to them that you have not.

What does good 360 feedback look like?

Behavioural and situational rather than adjectival. "Poor communicator" is unusable; "presents conclusions without the reasoning, so people agree without understanding" can be acted on. Brief contributors explicitly to describe situations, or you will receive a list of adjectives.

How is 360 feedback different from a performance review?

A performance review evaluates and usually affects pay; a 360 develops and should not. Reviews come from one manager, 360s from several groups with responses aggregated. Attaching a 360 to compensation is the most common way organisations destroy its usefulness, because contributors then answer strategically.

How do you use 360 feedback for leadership development?

Run it before the development work as a baseline, pick one theme rather than the five or six the report surfaces, tell your contributors which one you chose, and re-run it in nine to twelve months. The report itself changes nothing; the conversation afterwards is what does.

How often should 360 feedback be done?

Every nine to twelve months for someone actively working on development. More often measures novelty rather than change and creates survey fatigue among contributors. Less often and the specific incidents people were reacting to have faded from memory.