What gets counted and what gets heard

Organisations are extraordinarily good at counting things. Injuries, near misses, audit findings, compliance rates, days since the last incident. The infrastructure for measurement is impressive.

And yet some of the most important signals never make it into any of that. The unease a technician carries into a job but doesn't quite know how to name. The hesitation before signing off. The workaround that's been in place so long nobody remembers what it was working around. The pressure that's been building quietly in a team for months. These things are real, they affect outcomes., but they don't have a field in the reporting system, and by the time they show up in aggregated data, if they ever do, something has usually already gone wrong.

This is not an argument against measurement. Some things absolutely should be counted, tracked, and treated seriously. The problem is when we begin mistaking what is measurable for the totality of what is meaningful. A low injury rate may tell us something genuine. It may also create a comforting sense of control while more systemic signals remain difficult to see or discuss. Both things can be true at the same time.

A friend of mine works as a kind of discovery agent inside a large organisation, surfacing stories and operational realities from across the system. Once a month he shares some of those stories with the board. He told me the response is almost always the same:

"We're so grateful for you sharing this with us. But we kind of wish you hadn't."

And yet the board keeps inviting him back.

That sentence captures something important about what genuine organisational insight actually costs. It doesn't arrive pre-interpreted, pre-packaged, or translated into a neat recommendation for improvements. It asks something of the people who receive it. It requires them to sit with complexity, to revise assumptions, to see their organisation with more clarity and less distance than is always comfortable.

That discomfort is often a sign that the stories and insights you’ve generated are valuable.

This week I was asked how one can demonstrate the value of conversations to people who are used to counting things.

My honest answer is that the value shows up, but not always in the ways those people expect. It shows up when someone's questions change, when a leader who used to ask "are we compliant?" starts asking "where is the friction, and what is it telling us?" It shows up when the tone between frontline and leadership shifts from them-and-us toward something more like a shared attempt to understand the system together. It shows up when people are surprised in useful ways, not destabilised, but genuinely seeing something they hadn't been able to see before.

These things are harder to put in a report. But they're also harder to ignore when you see them.

Daniel