Most dashboards get ignored after the first look. That is a requirements failure, not a technology one. The one question to ask before you build the next.

A dashboard nobody opens is not a tool problem

Somewhere in your organisation is a dashboard that took three weeks to build and has been opened twice. It is not alone. The figures float around the industry like weather: adoption stuck around a fifth, most reports ignored after the first look, the rest quietly becoming wallpaper with a refresh schedule. The fashionable conclusion is that business intelligence is moving out of BI tools. We agree with where that is heading. We disagree, firmly, about why dashboards fail.

In practice, this is where our data strategy and leadership work comes in, and Why The AAP Is Not A Traditional Retainer covers useful related ground.

A dashboard nobody opens is almost never a technology failure. It is a requirements failure, and an expensive one, because you paid for the build, the licences and the training before anyone noticed it was decorative.

The question that gets skipped

Near the start, someone should have asked the only question that matters and usually nobody does: what decision does this change, who makes it, and how often. Three parts, one sentence. If you cannot answer all three before building, do not build. You will produce a handsome page of charts answering questions nobody asked, for people who were never going to do anything differently on a Tuesday as a result. That is not Power BI's fault. You can build the same useless artefact in any tool ever made, and most organisations keep a folder of proof.

A report is a cost until someone acts on it

Worth sitting with this one. A report is a cost right up until someone makes a different decision because of it. Until that moment it is not an asset, it is a tidy liability with hosting fees. So here is a blunt, free thing to do this week. Open your usage metrics, find every report nobody has touched in ninety days, and switch them off. Quietly. Then wait. The ones that draw a complaint were doing something. The ones nobody misses were never working, and you have just stopped paying to keep them alive. Most teams carry more dead reports than live ones and have never looked, because building gets applauded and pruning does not.

Into the working day, same discipline

Pushing intelligence out of the dashboard and into the flow of work is the right direction. An alert in Teams when a project crosses a line. A figure that turns up in the Monday operations meeting without anyone opening anything. An answer given in plain English the moment the question is asked. We are all for it. But it sharpens the question rather than dissolving it: put a number straight into someone's day and you had better know precisely what you expect them to do about it, or you have simply invented a faster way to be ignored.

This is why we run the Analytics Acceleration Programme from the decision backwards, never from the dataset forwards, and why our analytics strategy work spends as much effort deciding what not to build as what to. The measure of a BI investment was never reports shipped or how good they looked. It is decisions changed. Count those, prune everything that changes none, and aim the next build at a decision you can name out loud. Fewer dashboards, more decisions. The wall of dusty reports was never the goal, whatever it cost to put up.

If any of this sounds familiar, talk to us about your data.

Related reading

• A Fixed Price For Unscoped Work Is A Red Flag
• Stop Counting Dashboards. Count Decisions.
• What The Pub Trade Teaches About Your Numbers