AB Knovo All articles
Opinion

The Quiet Cost of Dashboards No One Reads Anymore

AB Knovo
The Quiet Cost of Dashboards No One Reads Anymore

Photo: Loominade, CC0, via Wikimedia Commons

There is a particular kind of corporate waste that never appears in a budget review because it hides inside a line item nobody questions: the analytics platform renewal. It's always justified. "Data-driven culture," the deck says. "Single source of truth," the vendor says. And yet ask a simple question — when did this dashboard last change a decision? — and the room goes quiet.

I'd argue that most mid-size and enterprise companies are paying for analytics infrastructure that stopped informing anyone months ago. Not underused — abandoned. Polished, refreshed nightly by an ETL job nobody audits, and read by no one.

The Dashboard Graveyard Is a Budget Line

Consider the arithmetic. A mid-size firm running a modern BI stack — licenses, data warehouse compute, a small analytics team — can easily spend $600,000 a year. Industry surveys and our own conversations with operations leaders suggest that somewhere between a quarter and half of the reports produced inside a typical organization see no meaningful readership after the quarter they were built.

That is not a technology problem. It is a decision-hygiene problem. Dashboards are created for a launch, a board meeting, a crisis. The crisis passes. The dashboard remains, quietly consuming warehouse compute and analyst hours on maintenance that serves no one.

We treat dead inventory ruthlessly. Nobody defends a warehouse aisle of unsold stock by saying "we might need it someday." But a stale KPI report gets an indefinite stay of execution because deleting it feels like admitting the original investment failed.

The Quarterly Report Audit

The fix is unglamorous and effective: a standing quarterly exercise that treats reports, alerts, and KPIs like inventory with a shelf life. Here is the version I've seen work:

1. Pull the usage logs. Every BI tool tracks views and query volume. Export it. Any dashboard with fewer than ten unique viewers in ninety days is a candidate.

2. Ask the owner one question. Not "is this useful?" — everyone says yes. Ask: "What decision changed because of this report in the last quarter?" No answer means it is decoration.

3. Build the kill list. Archive aggressively. Anything not deleted outright gets a six-month probation with a named owner and a stated decision it serves.

4. Reinvest visibly. Retired reports free up analyst time and compute. Announce what was killed and what the freed capacity now supports. This is the step most organizations skip, and it's why the exercise rarely sticks — audits without reinvestment read as cost-cutting theater.

What It Looks Like in Practice

A mid-size logistics firm I reviewed last year ran this drill across roughly 340 active dashboards. The usage logs were blunt: 118 had fewer than five viewers in a quarter. Another 60 duplicated reports that already existed in the finance team's stack — a redundancy born of two departments buying tools independently during a growth spurt.

The team archived just under half the inventory. The result was not merely tidier: warehouse compute dropped enough to cut BI spend by roughly a third at the next renewal, and the analytics team — previously the department of dashboard requests — redirected two full heads to a forecasting problem the COO actually cared about. Nothing of decision value was lost. Nobody noticed the missing reports for weeks, which is itself the most damning data point in this entire piece.

The Objection, and Why It Fails

The predictable pushback: "Some reports are only needed occasionally." Fine. Then they don't need a live, auto-refreshing pipeline. Archive them and regenerate on request. "Executives like having the data available." Executives like making good decisions; a wall of unopened charts contributes nothing to that.

The deeper objection is cultural — the fear that killing a report admits the money was wasted. Reframe it. The investment bought you an answer, possibly the answer "we don't need this." Sunk cost is not a maintenance contract.

A data stack should be pruned like a portfolio: ruthlessly, quarterly, with usage as the only witness that matters. The alternative is paying six figures for a museum of decisions you already made.

All Articles

Related Articles

Launch and Forget: The Institutional Amnesia Behind Your Worst Business Calls

Launch and Forget: The Institutional Amnesia Behind Your Worst Business Calls

The Meeting Purge: Seven Recurring Events to Kill Before Q-End

The Meeting Purge: Seven Recurring Events to Kill Before Q-End

The Forever Pilot: How 'Testing' Became Corporate Procrastination

The Forever Pilot: How 'Testing' Became Corporate Procrastination