Anonymity

The anonymity threshold explained: why 4, and what it protects

Key points

  • A threshold hides results for any group until enough people in it have answered.
  • With 3 answers one person can work out the others far more easily than with 4 or more.
  • No threshold stops a comment from giving its author away, so tell people to leave out names and specifics.
  • Managers must never guess or ask who wrote what.

An anonymity threshold is the minimum number of responses a group needs before any result for that group is shown. In Retrain and Retain it is 4 by default. This article explains why that number, what else protects people, and what no threshold can fix.

What a threshold is

Imagine a survey that shows a team's results as soon as one person answers. That person's answer is the team's answer, and anyone looking knows exactly what they think. A threshold prevents this. Below the minimum, the dashboard shows "not enough responses yet" and no numbers at all, not even partial ones.

The rule applies to every group view: a team, a dimension, a single question and a list of comments. What counts is the number of people who responded in that pulse, not the number invited. A team of 10 where 3 people answered has 3 responses, and with a threshold of 4 it shows nothing.

Why 4 is the default

The logic is arithmetic about guessing. Say three people answer a statement and the dashboard shows a score of 75, which is an average answer of 4.0 on the 1 to 5 scale. The answers add up to 12. If you are one of the three and you answered 3, the other two must add up to 9, which means one answered 4 and the other answered 5. You now know that both colleagues were favorable. With three responses, one person who knows their own answer can often pin down the others.

Now make it four responses with the same average of 4.0, which means the answers add up to 16. If you answered 3, the other three add up to 13. That could be 5, 5 and 3, or 5, 4 and 4, in several orders. You still learn something about the group, but you cannot pin down any one colleague. At four or more, the number of combinations that fit a result grows quickly and guessing gets hard.

There is a trade-off, and 4 is a balance, not a law. Every increase in the threshold protects people better and hides small teams sooner. A team of 6 with a threshold of 4 needs two thirds of its people to answer. With a threshold of 6, every one of them must answer, and a single skipped survey blanks the whole team.

What else protects people besides the number

The threshold is one layer. These are the others:

  • Nothing identifying is stored with an answer. Answers are saved without a name, email address, IP address or exact time. Only the date is kept.
  • Participation and answers are separate. The system records that an invited person has responded, so reminders stop. It never records what they answered, and there is no link between the two.
  • Comments follow the same rule. A comment from a team below the threshold is not shown anywhere, to the manager or to anyone else.
  • A guard against subtraction. If a manager leads a large team and a small team, showing the combined result alongside the large team's would let someone subtract to find the small team's. When that could happen, the small team is left out of the combined view.
  • Participation is counts only. You see how many of how many answered, never a list of who has not.

You can read more about how data is handled on the security page.

What a threshold cannot do

Be honest with your team about the limits.

  • Writing can give people away. A comment can identify its author through a detail only a few people know, such as a specific shift, an event, or a phrase someone always uses. The threshold protects the source of a comment, not its content.
  • Unique roles stand out. If one person is the only night-shift educator, a comment about nights points to them whatever the count.
  • Unanimous answers reveal the group. If every respondent gives the same answer, everyone's answer is visible, though none can be tied to a particular person.
  • People guess. No software stops a manager from deciding who wrote something. That is a behavior problem, and the last section deals with it.

When to choose 3, 5 or more

Organizations can set the threshold anywhere from 3 to 10.

  • Choose 3 when teams are very small and the real choice is between weaker protection and no results at all. Do it knowingly, tell people, and lean harder on comment hygiene.
  • Keep 4 as the starting point for most organizations.
  • Choose 5 or higher when topics are sensitive, trust is fragile after layoffs or a conflict, teams are close enough that people recognize each other's views, or comments tend to carry identifying detail.

Do not raise it just to look careful. If most of your teams can never see results, the survey stops serving them. Teams below the threshold are not shut out of listening: they still have 1:1s and team conversations. The empty cells that result are explained in reading a team heatmap without overreacting.

What to tell your employees

Say it plainly, limits included. Swap in your own threshold number if it is not 4.

This survey is anonymous. Your answers are saved without your name, your email or the exact time you answered, and I cannot see who said what. Results only show when at least 4 people on the team have answered, so no single answer stands out. One thing to watch for yourself: if you write a comment, leave out names and details that only you would know, because those can give you away even when the system cannot. I will never try to work out who wrote what, and I ask that we not guess about each other either.

Deliver it in person, then in writing, as part of the announcement described in how to run a two-minute manager pulse.

Four commitments for managers, starting this week

  1. I will not guess who wrote a comment. Not aloud, not privately, not as a joke. One guess that gets repeated ends honesty for everyone.
  2. I will not ask people to tell me their answers. Offering is fine. Asking is pressure.
  3. I will respond to the team, not to an author. If a comment stings, I thank the team, then work on the substance.
  4. I will not hunt for a way around the minimum. No splitting the team into smaller groups to see "just the nights result."

Read these out to your own boss, too. The protection only holds if the people above you keep the same rules.

Written by the Retrain and Retain team. This guide is general information, not legal, clinical or HR advice for your specific situation.

Give every manager a clear next step.

Start a free 90-day pilot with up to 3 managers, or explore the live demo with sample data first.

No credit card required. Employees are always unlimited.