Results and analytics

Analytics becomes available after summarizing the measurement. It shows not just the average score, but a working picture: where the team feels stability, where there is tension, and what topics need further discussion.

Results are needed for the See stage in the Ask → See → Discuss → Verify cycle. Their task is not to find someone to blame, but to show what the team should work on.

Levels of result

The platform calculates results at three levels: organization, team, and participant.

The organizational level shows the big picture for the measurement: overall score, summary, strengths, and tension zones. It helps the change initiator understand where the organization should focus.

The team level shows differences between teams. This is useful when the process is stable in one part of the organization, but the same topic creates tension in another. Team analytics depends on the structure of teams and the selected survey audience.

The personal result helps the participant understand their own response. It is separated from management analytics: the personal picture does not turn into a control tool and is not mixed into general conclusions.

What is visible in metrics

Scores show the direction of the state, but do not explain the cause by themselves. Therefore, next to numerical results, summaries, answer distributions, and semantic groups of similar comments appear.

Questions and categories help read the picture in layers. A category shows a general topic block, a question reveals a specific point of tension, and textual summaries explain what is behind the score.

If the measurement has a previous snapshot, the platform shows the dynamics. Comparison helps to understand whether the tension has gone after working with growth points, or whether the chosen approach needs to be changed.

How to read analytics

Start with the overall result, but do not stop there. The average score may look calm, even if a specific team or category has dropped. The point of analytics is exactly not to hide a weak spot behind a general number.

Then look at teams, categories, and questions. If the same topic repeats in different places, it is a good candidate for discussion as a growth point. If the tension is visible only in a narrow breakdown, the solution is also better sought closer to this breakdown, rather than launching a general reform.

Textual summaries should be read as a map of causes, not as literal quotes from participants. The platform protects raw answers and shows a generalized meaning.

Privacy boundaries

Raw answers are not shown to anyone. Only anonymized answers, aggregates, and summaries are shown in analytics when there is enough data for safe display.

Different thresholds apply for different details. List fragments are hidden with a very small number of answers; distributions and semantic groups require a denser sample. If the threshold is not met, the platform does not show this breakdown or replaces it with a more general picture.

This limitation is not a report error. It protects trust in the survey: participants can answer honestly, and the team works with the big picture, rather than trying to find out who said what.