Data
Why dashboards go unused, and what to do about it
Most dashboards die within months. The fix is less about visualization and more about definitions and ownership.
Every agency has a graveyard of dashboards. They were launched with enthusiasm, viewed for a few weeks, and then quietly abandoned. The cause is rarely the charts.
Reason one: nobody agreed on the numbers
If the operations dashboard says one thing and the finance report says another, people stop trusting both. Before building anything, agree on definitions. What counts as a "closed" service request? Which date is the response time measured from? Write those definitions down and put them on the dashboard.
Reason two: no owner
A dashboard needs a person responsible for its accuracy and relevance, who checks it, answers questions about it, and retires it when it stops being useful. Without one, the first data pipeline failure goes unnoticed and the dashboard becomes wrong, then ignored.
Reason three: it does not answer a decision
Dashboards that show everything answer nothing. Start from the decisions a manager makes weekly and build for those. A director who has to decide where to assign inspectors needs a backlog by district, not thirty tiles.
Reason four: the data is late or broken
If the pipeline runs monthly, the dashboard is a report, not a tool. If it breaks silently, it is a liability. Pipelines need monitoring, and staleness should be visible on the dashboard itself.
Reason five: it lives in the wrong place
If the dashboard is not where people already work, they will not go looking for it. Embed it in the intranet, send a weekly snapshot, or put it in the meeting where the decision is made.
What we do differently
We start every reporting engagement with a metric dictionary and an owner for each measure. We build pipeline monitoring before we build charts. And we design a dashboard for a specific meeting or decision, then measure whether it is used. If it is not, we change it or retire it.