Why your dashboard exists but nobody opens it

A dashboard that was exciting at launch and forgotten within a month is one of the most common outcomes in business software — and almost always for the same reason: it was built to show data, not to answer a question anyone actually has.

The gap between "accurate" and "useful"

A dashboard can be technically correct — every number pulled live, every chart rendering properly — and still be useless, if the numbers it shows aren't the ones the person looking at it actually needs to make a decision. An owner checking a dashboard once a week isn't looking for data; they're looking for an answer to a specific question: are we on track, where's the risk, what needs my attention today. A dashboard full of metrics that doesn't clearly answer that gets opened less and less.

Why this happens during the build

Dashboards are often designed around what's technically easy to display — whatever data is already in the system — rather than around what decision the dashboard is meant to support. The result is a screen full of numbers that are each individually true but collectively don't tell anyone what to do next.

What makes a dashboard actually get used

Start from the decision, not the data. Ask what question this specific person needs answered, how often, and what they'd actually do differently depending on the answer. Build backward from that to the handful of numbers that matter, and leave the rest out — even if it's technically available and "might be useful someday."

A quick test for an existing dashboard

Ask the person it was built for what decision they made last week because of it. If the honest answer is "none," the dashboard isn't broken technically — it's answering a question nobody's actually asking.