People Aren’t Dashboards: Where Data-Driven Leadership Goes Wrong

I like data. That feels worth saying before this turns into something that sounds like an argument for throwing away KPIs and managing by intuition.

Good data improves decisions. It reveals patterns, challenges assumptions and can surface a problem before it becomes obvious. The trouble begins when “data-driven” stops meaning “I use data to understand reality better” and starts meaning “if I cannot measure it, it does not exist”.

A dashboard sees the signal. It does not know the story.

Engagement drops. Attrition rises. Utilisation misses target. Team velocity falls for a third sprint. Sick leave increases.

These are useful signals. None of them comes with a built-in explanation.

Lower velocity could mean harder work, technical debt, poor requirements or a conflict nobody has named yet. Higher absence might reflect seasonal illness, workload or something entirely unrelated to the team. Attrition tells you people are leaving. It does not show the moment someone mentally checked out three months before submitting a resignation.

Dashboards are excellent at showing movement between points. They are much less capable of telling you what happened in the space between them.

A metric is a representation, not the thing itself

An engagement score is not engagement. Ticket count is not productivity. Hours booked to a project are not value. Number of one-to-ones is not leadership quality. Office attendance is not collaboration.

Any of those numbers may be useful. Every one of them is a proxy.

That is fine until the proxy becomes the definition. At that point, the leadership question quietly changes from “what is happening here?” to “how do we move the number?”

Those questions are not the same.

When the KPI becomes the goal, people learn to optimise the KPI

Set utilisation at 90% and an organisation can often produce a beautiful 90%. The more interesting question is what else it produces along the way.

Perhaps there is less time for learning. Less space to help a colleague. More effort spent booking work where it looks best. Less attention to important activity that does not have a project code attached to it.

The same dynamic appears with ticket volume, lead time, client meetings or office presence. People are remarkably adaptive. They learn what the system rewards and adjust behaviour accordingly.

You may therefore get exactly the number you asked for and something quite different from the outcome you wanted.

Data-driven leadership is not people management through Excel

The most useful leadership data usually creates curiosity.

“Utilisation dropped. What changed?”

“Two teams have very different engagement results. What is different about how they work?”

“Escalations are increasing. Is that a quality issue, a decision-rights issue, or are people becoming less willing to take a risk without managerial approval?”

Now the metric becomes the beginning of the conversation rather than a replacement for it.

That matters because many things that eventually affect performance show up qualitatively first. Someone stops challenging decisions. Difficult topics move from the team meeting to private chat. One person becomes the unofficial bottleneck. People wait for the manager even when they technically have authority to decide.

None of this is guaranteed to appear on your dashboard immediately.

Not everything important needs to become a target

Organisations have a natural instinct: if something matters, measure it. If it matters a lot, give it a target.

Some things become distorted when reduced too quickly.

Psychological safety can be researched, observed and discussed. It is harder to “deliver 82% psychological safety” in any meaningful sense. Decision quality matters, but counting decisions tells you very little about whether they were good. One-to-ones matter, but four calendar events a month are not evidence of four useful conversations.

Data maturity is not the ability to produce a metric for everything. It is also the ability to recognise when a metric is a strong signal but an incomplete explanation.

The most data-driven question may be the one after the number

“What is the result?” is useful.

“What does this result actually represent, and what might it be missing?” is better.

That is not anti-data. It is a more disciplined relationship with data.

Numbers can tell us that something changed. Human context helps us understand what the change means.

Which is why people are not dashboards.

If your work sits at the intersection of metrics, decisions and people, Leadership Coaching can create space to examine what happens between the number and the decision.