Team Survey results (health check, maturity survey and custom surveys) show more than the overall score: statistical metrics such as answer spread or block weight also appear on the page. Here is what each of them means, with worked examples.
Maturity index / Team pulse
The overall survey score — a weighted average of the block scores. Each block in a survey has its own weight (see "Block weight" below): the block score is multiplied by that weight, the products are summed and divided by the total weight. A block with no scored (scale) questions — only choice, text, or unanswered questions — is excluded from the calculation. For a health check with a traffic-light scale, the same metric is labeled "Team pulse".
Team variance (answer spread)
This shows not the average score, but how much individual team members' answers diverge around that average. The number is not normalized to a 0–1 range and has no inherently "good" value — its unit is the same as the question's own answer scale (usually 1–5).
How it is computed:
- for each question — the standard deviation of all respondents' answers to that question;
- for each block — the average of those deviations across the block's questions (the same number shown in the "Variance" column of the block scores table and in the "Spread" column of the question heatmap);
- Team variance — the average across all of the survey's blocks.
Example: if on a question half the team scored 2 and half scored 4 (average 3), the spread comes out to exactly 1.0 — as if the team split into two subgroups, each one point away from the average.
A rough guide for a 1–5 scale (a 4-point range):
- 0 — full consensus, everyone answered the same;
- ≈0.3–0.6 — tight agreement, a small spread of opinions;
- ≈0.8–1.2 — noticeable disagreement: part of the team sees the situation differently than the rest;
- ≈1.5 and above — strong disagreement, close to the team splitting into two camps.
Team variance is an average across many questions and blocks at once, so the same value can hide different pictures: even light noise spread across every question, or one or two sharply divided questions sitting next to consensus on the rest. To see where the spread actually comes from, check the "Variance" column in the block table and the question heatmap on the result page.
Block weight
The coefficient with which a block's score counts toward the overall survey index. It is set when creating or editing blocks in the survey template. A block with a higher weight influences the overall maturity index / team pulse more than a block with a lower weight, even if both blocks have the same average score.
Baseline (survey wave)
A free-text label for a measurement wave (e.g. "Q1 2026") set by whoever launches the survey — it is shown on the result page and in the wave history. The wave-comparison history (trend, index change, degradation signals) is not built from this label: it is built from the fact that these are surveys of the same team using the same template, ordered by launch date. It's enough to pick a template once and relaunch it repeatedly — the baseline label itself can be changed or left empty as you like.
Degradation signal
A warning that a block's score dropped noticeably compared to the previous wave — the decrease exceeded a threshold configured at the installation level. The signal has two severity levels, "medium" and "high", depending on how much the score dropped. It is only shown when the previous wave collected enough responses for a reliable result.