Dashboards

Reading a team heatmap without overreacting

Key points

  • Read rows first, then columns. A column that is low everywhere is an organization issue.
  • Small teams swing: one person changing one answer can move a score by several points.
  • Wait for a pattern over two or three pulses before you act.
  • Never turn the heatmap into a ranking of managers.

A team by dimension heatmap shows you where to look. It does not tell you who is failing. Read it patiently, over several pulses, and it points to the conversations worth having. Read it as a scoreboard and it does damage.

What a cell tells you

On the executive dashboard in Retrain and Retain, each row is a team and each column is a dimension, such as Psychological Safety, Recognition or Workload & Burnout. Each cell shows a score from 0 to 100. The score is the average answer on the 1 to 5 scale, rescaled so that a 1 becomes 0 and a 5 becomes 100. The bands are simple: 75 and above is "strong," 60 to 74 is "steady," and below 60 is "needs attention."

Two details prevent a lot of confusion. A score of 50 does not mean "half of people are happy." It means the average answer was a 3, which is neutral. And "favorable," the share of people who answered a 4 or 5, is a different measure from the score. Both are useful. Do not mix them up in the same sentence in a meeting.

Read rows first, then columns

Start with a row: one team across all dimensions. Is the whole row soft, or is it one dimension? A team that is low only on Workload & Burnout and fine elsewhere has a specific problem, often a staffing or scheduling one. A team that is low across the board is telling you something broader about how it is led or supported.

Then read the columns. A column that is low for nearly every team is not a manager problem. If Staffing & Resources or Career Development is weak almost everywhere, the cause probably sits above any single manager: budget, hiring, pay structure, a missing career ladder. Sending those managers off to "improve their scores" wastes their time and costs you credibility. Fix it at the level where the cause lives.

Small teams swing

A small team's score moves a lot for ordinary reasons. Take a team of 6 where everyone answered. One person changing one answer by one step on the 1 to 5 scale, say from a 3 to a 4, moves that statement's score by about 4 points. If someone has a rough week and drops from a 5 to a 2, that one answer moves the score by 12.5 points. The table shows the arithmetic for a single statement.

People who answeredOne person moves one stepOne person moves three steps
46.3 points18.8 points
64.2 points12.5 points
122.1 points6.3 points
300.8 points2.5 points

What counts is the number of people who answered, not the size of the team. If only 4 of 8 people responded, each answer carries the weight shown in the first row. Now look at the band lines. The "steady" band is only 15 points wide (60 to 74), so a team of 6 sitting at 62 can fall into "needs attention" because one person had a worse month. That is not a change in the team. It is a change in one person's mood on one day.

Wait for a pattern

One pulse is a photograph. Two or three in a row are a direction. A team that dips for one pulse after a hard month, a system go-live or a manager's leave usually recovers by itself. A team that falls two pulses in a row, with comments naming the same thing, has a real problem. Read the change since the last pulse before you read the color.

Look at participation too, which is always shown as counts of how many of how many answered. Falling participation across pulses is information in its own right: people have stopped believing it matters. The retention risk signal on the dashboard rolls several measures together, including falling scores over two pulses and participation, into low, moderate, elevated or high. Treat it as a signal about a team, not a forecast about any person.

What empty cells mean

An empty cell marked "not enough responses" means fewer people answered than the anonymity threshold, which is 4 by default. It does not mean the team is hiding something, and it is not a bug. It is the protection working. Do not try to guess the missing number from the cells around it, and do not push a manager to "get more people to answer" in a way that puts pressure on individuals. Ask instead what would make people trust the survey more, and watch the participation counts over time. The reasoning behind the number is in the anonymity threshold explained.

One red cell, and the ranking trap

When a single cell is below 60, resist the urge to call the manager. Work through it in order:

  1. Check how many people answered. A red cell from 4 people is weaker evidence than one from 25.
  2. Check the previous pulse. Is this new, or has it been there for a while?
  3. Read the comments for that team. They appear only when the threshold is met.
  4. Ask the manager what they are seeing before you show them the number.
  5. Offer support first: time, a coach, a decision they have been waiting on.

Then there is the ranking trap. It is tempting to sort managers by score and congratulate the top. Do not. Teams differ in size, shift mix, acuity and tenure, and a night unit and a day unit are not the same job. Ranking turns a conversation into a contest, and managers respond to contests by coaching their teams on how to answer. Compare a team with its own past, not with the unit next door.

A five-step routine for your next leadership meeting

Thirty minutes a month is enough if you keep the order:

  1. Participation. Which teams are above the threshold, and which counts changed since last time?
  2. Rows. Which teams show a falling trend over two pulses or more? Pick three at most.
  3. Columns. Is any dimension low across many teams? That is an organization item, so give it an owner and a date.
  4. Comments. For the teams you picked, read the comments. What do people say in their own words?
  5. Decide. For each item, one decision, one owner, one date. Offer support to the manager, then check the next pulse.

To practice before you have your own data, open the live demo with sample data and run the routine on it. When a team's comments point to something specific, turning a comment into an action plan is the next move.

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.