Against the dashboard

The last decade of operational tooling has been an enormous investment in seeing. Warehouses, BI layers, real-time dashboards, alerting on everything. The premise was that better visibility produces better operations. It has not, particularly, and it is worth asking why.

Seeing is not the constrained resource

In most organisations the number was always available to someone. The problem is the distance between the number appearing on a screen and anything happening as a result. That distance is measured in meetings, hand-offs, and the availability of the one person who knows what to do about it.

Adding another dashboard shortens the first metre of that journey and none of the rest. This is why dashboard proliferation correlates so poorly with operational improvement, and why the twelfth dashboard is reliably less useful than the first.

Closing the loop

The interesting question is not what should we watch but what should happen automatically when this is true. That reframing is uncomfortable because it forces specificity. 'Monitor supplier risk' is a dashboard. 'When a supplier's delivery variance exceeds this threshold, pause new orders and route to this owner with this evidence' is a system.

The second one can be wrong, which is precisely why it is more valuable. It commits to something. A dashboard never has to be right because it never has to decide.

Where visibility still earns its place

None of this argues for flying blind. It argues for a different consumer of the signal. Instrumentation aimed at a human should answer a question that human is going to act on; instrumentation aimed at the system should be complete, structured, and continuous. Confusing the two produces dashboards nobody reads and automation with nothing to reason from.

The test we apply internally: if this chart were removed tomorrow, would any decision be made differently? For most charts, honestly, no.