March 20266 min readOperations
Why most operational dashboards fail
Every operations team has a dashboard. Most of them are ignored.
The pattern is familiar: a well-intentioned transformation lead commissions a dashboard from the BI team. Requirements are gathered. Stakeholders are consulted. A polished product is delivered — complete with filters, drill-downs, and a colour palette that matches the corporate brand. Usage spikes for two weeks, then flatlines.
The problem is rarely technical. It is a design problem — specifically, a failure to understand how operational managers actually consume information.
Operational managers do not sit in front of dashboards waiting for insights. They are in meetings, on calls, responding to escalations. The information they need must come to them, not the other way around. A dashboard that requires someone to log in, navigate to the right view, and interpret a chart is already asking too much.
The most effective operational reporting tools share three characteristics. First, they are exception-based: they surface what is wrong, not what is right. A green-light dashboard that shows everything is fine provides no value — it just confirms the absence of known problems. Second, they are push-based: alerts, automated emails, Slack notifications that arrive when attention is needed. Third, they are actionable: each alert includes enough context to act on it without further investigation.
This does not mean dashboards have no place. They are excellent for strategic reviews, trend analysis, and committee reporting — contexts where someone has dedicated time to explore data. But for day-to-day operations management, the humble automated email often outperforms the most sophisticated Tableau deployment.
The lesson is broader than dashboards. Every tool we build should start from the question: how does the user actually work? Not how do we think they should work, or how the process document says they work, but what do they actually do when they sit down on Monday morning? Start there, and the right design usually becomes obvious.