← Blog

Anonymous 360 feedback: why everything depends on the trust of those who answer

30 October 2026

A 360 review, also called 360 feedback, asks for something delicate: that someone speak candidly about their manager, a colleague or someone who reports to them. If that person suspects they can be identified, they don’t lie, but they soften. And a 360 full of softened answers is worthless.

That’s why, before the questions, the scale or the report design, what decides whether a 360 works is anonymity. And promising it isn’t enough: it has to be guaranteed by how the results are calculated and shown.

When raters hesitate, the report goes flat

People who don’t trust the anonymity rarely say so. They just answer differently: they score everything in the middle, avoid the extremes, and leave comments blank or write something generic like “great colleague, keep it up”.

This isn’t just intuition. In a classic study, Antonioni (1994) compared employees who rated their manager anonymously with others who knew the manager would see who had answered what. Those who were identified gave higher ratings: when there’s something to lose, feedback gets inflated. Waldman, Atwater and Antonioni (1998) also report that some raters openly admit they would raise their scores if they were going to be identified.

The result is a flat report. Averages look alike across competencies, blind spots don’t show up, and the person being reviewed is left feeling that “everything is more or less fine”. The exact opposite of what they were looking for.

The cost shows up in the debrief. With no clear gaps between how someone sees themselves and how others see them, there’s nothing to talk about. And the next time a 360 is launched, people take part with even less enthusiasm.

Three ways an “anonymous” 360 gives someone away

Many tools hide the rater’s name and consider anonymity solved. But you don’t need a name to know who said what.

  1. Groups that are too small. If the person being reviewed has two direct reports and the report shows the “direct reports” average, each of them can work out what the other scored. With only one, anonymity doesn’t even exist.
  2. Averages you can subtract. Suppose the report shows the peers’ average, the direct reports’ average and an overall average that also includes a group hidden for being too small. With a little arithmetic, the hidden group appears: if the 6 visible raters average 4.0 and the overall average of 7 raters is 3.7, the hidden answer is 1.9 (7 × 3.7 − 6 × 4.0). Hiding a number is pointless if it’s still inside another one.
  3. Comments that give themselves away. A comment in Catalan when only one person on the team writes in Catalan. A comment dated on a day when only one person answered. Or comments shown in the order they arrived, when everyone knows who answered first.

None of these flaws requires bad faith. All it takes is someone reading the report closely, and the person being reviewed is precisely the one who will read it most closely.

How to keep a 360 anonymous: anonymity by design

The solution isn’t asking people not to look. It’s making sure the report doesn’t contain the data that would identify anyone. In Refleko we do it with four rules the system always applies, no exceptions:

An anonymous group with fewer than 3 answers never stands alone An anonymous group with fewer than 3 answers never stands alone What raters submit What the report shows Self-assessment 1 Manager 1 Peers 3 Other relationships 1 · under 3 Direct reports 3 Me identified Manager named, told in advance Peers + other relationships 4 answers: none can be singled out Direct reports 3 answers If a group doesn’t reach 3 even when combined, it is hidden and left out of every figure.
In this example, the single answer from “other relationships” is added to the peers’ answers, so none of the four can be singled out.

The effect is easy to explain to raters: it isn’t that someone promises not to look, it’s that there’s nothing to look at.

How to prepare a 360 so people answer candidly

The technical rules are necessary, but trust is also built by explaining them. If you run a 360 as a coach or from HR, these four steps make the difference:

  1. Explain the rules before anyone answers. In a short session or in the launch email: how many answers each group needs and what happens if it falls short.
  2. Say who will see the report. The person being reviewed, the coach, their manager if they choose to share it. No surprises later.
  3. Warn whoever will be named. If the manager will be identified, they should know before answering, not when reading the report.
  4. Check the groups before launching. If a group won’t reach the minimum, it’s better to widen or merge it now than to find out at the close.

A rater who understands the rules answers more candidly. And that candour is what gives the debrief its substance.

Frequently asked questions about anonymity in 360 feedback

Is a 360 review always anonymous?

Not entirely. Usually the self-assessment and the manager are named, while peers and direct reports answer anonymously. What matters is that every rater knows, before answering, which case they’re in.

How many raters does each group need?

Enough that nobody is singled out. The usual industry reference is a minimum of 3 per group, which is also Refleko’s minimum. With fewer, the group is combined with another or not shown.

Who can see individual answers?

In a well-designed 360, nobody: not the coach, not HR, not the person being reviewed. Only aggregated results are shown.

In short

A 360 doesn’t fail because of its questions; it fails when people don’t dare to answer them honestly. Guaranteeing anonymity by design, and explaining it well before you start, is what turns the answers into something useful for the person being reviewed.

References

Let’s talk

Planning a 360 for your team or your clients and want to clear up questions first? Write to us at hello@refleko.com or through our contact page.