How you get here
Dashboards are requested by the people who commission software and used by the people who do not. A manager asks for visibility, the request is entirely reasonable, and the result is placed at the front door because that is where important things go.
Then it spreads. Every section gets a summary strip. Every list gets tiles above it. Each addition is defensible and the cumulative effect is a product where the first screen of everything is a report.
How to recognise it
- The home screen has no action on it.
- Analytics show people leaving the landing screen within seconds, always towards the same list.
- Nobody can say what decision any given number would change.
- The numbers are exact where nobody needs precision, and absent where somebody does.
- Charts have three data points.
- Asked why a tile is there, the answer is "so people can see it", not "so people can decide something".
Why it fails
A number is only useful if it changes what someone does. Most dashboard tiles fail that test: revenue this month is interesting, and the person looking at it has no lever attached to it on that screen.
Meanwhile the actual work — the seven things waiting on this person — is one click away and invisible. So the product's most prominent surface is spending its position on the smallest audience, on every visit, for everyone.
There is a second cost. Because a dashboard is never finished, it provides no sense of completion. Software people work through feels different from software people look at, and the difference shows up in whether they open it.
The way out
- Ask what decision each number changes. If none, it is not a metric, it is trivia. Move it to a report someone visits deliberately.
- Put the work first. Most internal products should open on what needs the person, with the numbers reachable rather than resident.
- Attach an action to any number that survives. "$21,400 overdue" should be a link into the filtered list, not a tile.
- Do not chart three numbers. Print them.
- Give managers their own page. The reporting need is real; it just is not the same screen as the operator's front door, and pretending otherwise serves neither.
The distinction worth keeping
This is not an argument against dashboards. A dashboard is the right screen for someone whose job is monitoring — an on-call view, a live operations wall, a weekly review. The disease is not having one; it is making it the default answer to "what should this screen be", and putting it in front of people whose job is something else.
The test
Watch someone open the product. If the first thing they do is navigate away from the landing screen, that screen is a toll, not a home — and it is being paid by everyone, every day.