What a 360 review is, and whether you need one

A traditional review runs on one manager’s view, and a manager sees perhaps twenty or thirty per cent of what someone actually does. A 360 collects the rest: from peers, from direct reports, from the manager, sometimes from people outside the team entirely.

Who it asks, and when it is worth doing

Five sources: the person themselves, the manager, peers at the same level, direct reports if the person manages anyone, and cross-functional partners or customers where the work crosses a boundary.

It earns its cost in three situations: leadership roles, where the manager’s view is the least complete; roles that live between teams; and development for people the company is investing in. Outside those, a lighter form of peer feedback usually does the same job for a fraction of the effort.

What it gives you

A fuller picture, obviously. But the more interesting effects are the other three. Bias gets diluted rather than concentrated in one rater. The gap between how someone sees themselves and how everyone else sees them becomes visible, which is the single most useful thing a development conversation can start from. And managers finally hear something about what it is like to work for them.

Where it goes wrong, and the one rule

The rule first: use a 360 for development, never for evaluation or pay. The moment ratings affect money, people start managing their ratings instead of giving feedback, and the quality of what you collect collapses. This is not a nuance, it is the whole design.

Then the practical risks. The process is heavy, six to nine hours per participant once you count everyone’s time, so do not run it for everybody every year. Anonymous feedback removes accountability along with the fear, which is a trade rather than a free win. And the feedback itself is often vague or weighted toward whatever happened last month, which is a design problem: ask about observable behaviours, not adjectives.

Choose seven to twelve raters who genuinely work with the person. Deliver results in a conversation rather than a report, because a 360 read alone tends to land badly. And end on two or three commitments, not twelve.

Sign up for a free TalentRewards trial.