Averages are everywhere in people data. Average engagement scores. Average satisfaction. Average scores by department. They look helpful and feel objective. But when it comes to understanding how people actually feel about working at your organisation, averages often hide the very problems leaders need to see.
An average is designed to simplify. It takes a wide range of different experiences and turns them into a single number. The problem is that people do not experience work "on average."
When how people feel about working there shifts in one part of the organisation, an average often absorbs it rather than surfaces it. A small but significant change in a specific team or location can disappear inside a stable-looking overall score. The number does not lie - but it does not tell the whole story either. This is why organisations are sometimes surprised by problems that, in hindsight, had been visible in the detail for months.
Leadership teams often look at an average score and conclude that things are broadly fine, that nothing urgent is happening, and that the sensible course is to keep an eye on it. Meanwhile, one team is under sustained pressure, a manager is struggling, and frustration is building quietly in a part of the organisation that the average has rendered invisible.
Averages are comfortable. They reduce complexity and sidestep difficult questions. But they also delay difficult conversations, encourage a wait-and-see approach and make responsibility less clear. When the average looks acceptable, it is harder to justify early action - even when something does not feel right to the people closest to it.
In people data, the most important signals tend to sit at the extremes rather than the centre. Teams under sustained pressure. Groups where scores are falling quickly. Areas where how people feel about working there is moving in a direction that the overall number does not yet reflect.
Averages pull attention toward the middle and away from these edges. As a result, leadership conversations focus on headline stability rather than underlying movement - and movement is where the early warning is. A score that is holding steady overall while declining sharply in one area is not a stable signal. It is a masked one.
Leaders do not need more numbers. They need visibility into where how people feel about working at their organisation is changing, how fast it is moving and which areas need attention first. That requires looking beyond the headline average and paying attention to variation and direction of travel - not just whether the overall score is up or down.
This is not a complicated ask. It means treating the average as a starting point rather than an answer and building the habit of looking at what sits beneath it. This connects directly to How to spot early signals before they become problems.
Averages are not wrong. They are just blunt. When organisations rely on them too heavily, early warning signs get smoothed away and problems surface only after they have grown harder and more expensive to deal with. The number to watch is not the average - it is the movement underneath it.
Ready to see how your people feel about working at your company? Start your free cycle - no card, no commitment.
Also worth reading: Why a clear signal matters more than data