360 feedback measures perception. That’s useful — if you say so.
360-degree feedback collects ratings from peers, reports and managers. The research is clear that it measures perception, that its development value depends heavily on how it’s delivered, and that using it for pay decisions corrupts it quickly. This tool is built around those findings.
Where 360 programs go wrong, in order of frequency
Using them for evaluation is the first and worst error: once ratings affect pay or promotion, reciprocity and score inflation set in within a cycle, and the instrument stops measuring anything. Second is rater-set construction — too few raters, or raters chosen by the subject, produces noise dressed as insight. Third is delivery: raw scores handed over without facilitation reliably produce defensiveness rather than development, which the feedback literature has documented for decades.
A carefully built program addresses all three: development-only positioning stated and enforced, rater sets constructed with minimum counts and mixed sources, and results delivered with support rather than emailed as a PDF. The software’s job is to make the careful version the easy one — and to keep the honest framing visible rather than letting ‘insight’ language oversell what perception data can carry.
Rater sets built for signal
Minimum counts per source, mixed rater categories, and subject input balanced against manager oversight — the construction rules that separate signal from a popularity poll.
Anonymity that’s real, and stated
Aggregate thresholds prevent identification, and participants are told exactly what their subject will and won’t see — honest terms produce honest ratings.
Delivery designed against defensiveness
Results framed as perception data with facilitation prompts and development pathways — because the delivery decides whether feedback lands or triggers.
Every angle, safely gathered
Peers, reports and manager — anonymised, themed and delivered as growth input, not ammunition.
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Design the program before the survey.
Rater rules, use-case boundaries and delivery — the design session that decides whether the data will be worth collecting.
The evidence this page stands on
Questions buyers ask
Can 360 results be used in performance reviews?
They can be; the evidence says they shouldn’t. Once ratings carry consequences, the data degrades within a cycle or two. If your organisation insists, do it knowingly — and expect the instrument’s value to fall.
How many raters are enough?
Practically, five or more per source category for stable aggregates; below three, anonymity fails and noise dominates. The platform enforces thresholds you set.
Do 360s actually improve performance?
The meta-analytic picture is modest and highly conditional — improvement depends on delivery quality, follow-up support and the recipient’s initial reaction. Treat it as one input to development, not an intervention in itself.
What about upward feedback specifically?
Often the most valuable component and the most sensitive — anonymity thresholds matter most here, and small teams frequently can’t support it safely. The platform will tell you when the numbers don’t work.
Is this product available today?
Ask for the current release picture for the People product line — this page describes capability, not a shipping commitment.
See it on your own content.
Bring one course. We’ll show you the retention curve your current training leaves behind — and what scheduled review does to it.
- 30 minutes, on your calendar — pick a slot here
- Run on your own content wherever possible, not a canned deck
- You see the dashboards, the learner surface and the evidence exports
- No commitment — and pilot data stays yours either way