Somewhere in your organisation, right now, there’s a dashboard that nobody has looked at in three months. It was expensive to build. It took weeks of meetings to define the requirements. Someone spent days getting the SQL queries right. And now it sits there, loading data faithfully every morning for an audience of zero.

This is one of the most common wastes in business technology. Companies pour money into dashboards and most of them end up ignored.

The Problem Starts With the Request

Most dashboards are born from a senior leader saying something like “I want visibility into our sales pipeline” or “I need to see our marketing metrics in one place.” These are reasonable desires. The problem is what happens next.

A team — usually a mix of analysts, developers, and the IT department — goes away and builds what they think the leader wants. They interview stakeholders. They gather requirements. They create a spec document. Weeks later, a dashboard appears.

The leader looks at it, says “that’s great, thanks,” and opens it maybe three more times before forgetting the URL.

Why? Because the dashboard answers questions the leader didn’t actually have. It shows a bunch of numbers that are technically relevant but don’t connect to the specific decisions they’re trying to make. It’s like being given an atlas when you asked for directions to the airport.

Too Much Data, Not Enough Insight

The instinct when building a dashboard is to include everything. Sales by region, by product, by month, by quarter, by rep. Marketing spend by channel, by campaign, by week. Customer metrics by segment, by lifecycle stage, by NPS score.

The result is a wall of numbers that takes five minutes to scan and leaves you no more informed than when you started. Harvard Business Review has written extensively about how information overload paralyses decision-making rather than supporting it. Dashboards that try to show everything end up communicating nothing.

The best dashboards I’ve seen show three to five numbers. That’s it. The key metrics that tell you whether things are on track or off track, with the ability to drill down if something looks wrong. Everything else is noise.

Nobody Defined the Actions

Here’s the question that almost never gets asked during dashboard planning: “When you see this number, what will you do differently?”

If sales are down 10% this month, does that trigger a specific action? A conversation with the sales team? A change in pricing? A marketing push? If the answer is “I’ll just know about it,” the dashboard is a vanity project.

Useful dashboards are tied to decisions. Each metric should have a threshold — green means keep going, yellow means investigate, red means act. Without those thresholds, you’re just watching numbers move without a framework for responding.

One firm we talked to described it as the difference between a car dashboard and a car manual. Nobody reads the manual while driving. But when the fuel light comes on, you know exactly what to do. That’s what a good business dashboard should feel like.

The Maintenance Problem

Dashboards don’t maintain themselves. Data sources change. Business definitions evolve. That “active customer” metric made sense when you had one product, but now you have three and the definition is different for each.

If no one keeps a dashboard accurate, it degrades. One broken chart is all it takes for people to stop trusting it. And once trust is lost, they won’t come back.

What to Build Instead

Start with a question, not a tool. Don’t build a “sales dashboard.” Instead, answer a specific question: “Are we on track to hit our Q1 revenue target?” That’s a dashboard with maybe two charts and one number. It’s boring. It’s also useful.

Build for a routine. The best dashboards are part of someone’s workflow. The Monday morning check-in. The weekly sales review. The monthly board report. If there’s no routine that the dashboard plugs into, it won’t get used.

Make it ugly if necessary. Seriously. A Google Sheet that answers the right question is infinitely more valuable than a beautifully designed Tableau dashboard that answers the wrong one. Don’t let aesthetics drive the process.

Kill dashboards that aren’t used. Run a quarterly audit. Check who’s actually opening each one. If usage has dropped to zero, shut it down. Dead dashboards clutter your tools and make it harder to find the ones that matter.

Invest in alerts, not views. Instead of a dashboard people need to remember to check, send a notification when something goes wrong. Revenue dropped below target? Slack message. This pushes information to people instead of hoping they’ll pull it.

The Uncomfortable Truth

Most dashboards go unused because they were built to satisfy a request rather than solve a problem. The request — “give me a dashboard” — sounds clear but is actually one of the vaguest things you can ask for. The real work is figuring out what decisions it should support and building the minimum version that does exactly that.

Less exciting than an analytics masterpiece with interactive filters. But at least someone will actually use it.