Key takeaways
- The threshold is a product decision, not a slogan about trust.
- FeedbackPulse hides results until at least three people answer.
- A higher bar protects small groups and can hide the team you wanted to hear.
- I ask what a manager can see when the group is under the threshold.
People answer an engagement survey when they believe the result will not identify them. The product enforces that with a number. I look for the number before I look at the color of the dashboard.
The number is the feature
FeedbackPulse
FeedbackPulse’s homepage says survey results stay hidden until at least three people have answered. That is a low bar, and it matches a product aimed at teams that are not huge. A 12-person team can see a result. A team of two cannot, which is the point.
What the number trades away
Three responses in a team of eight is easier to guess than ten responses in a department of two hundred. I do not call one threshold safer in the abstract. I ask whether the grouping on the page matches the team that will read the result.
What I ask in the demo
- What is the smallest group that can see a score, and who sets the group?
- What does a manager see when the group is one response short?
Comments are a separate risk
A score can clear the threshold while a written comment still names a shift, a manager, or a project. I ask whether comments are shown with the score, held back, or editable before a manager sees them. The engagement guide asks a version of that question on each entry.