The tool is almost never the problem. When dashboards go unused, the cause is upstream: undefined metrics, untrusted data, or answers to questions nobody asked. Here's how to tell which one you have.
The pattern repeats across companies: buy Tableau, Looker or Power BI, spend a quarter building dashboards, hold a launch meeting. Six months later the CFO is still asking an analyst for one-off SQL pulls, and the license renewal is a line item nobody can defend.
The instinctive diagnosis is "wrong tool." In our experience running analytics engagements, it's almost never the tool. Unused dashboards have three root causes, and each has a different fix, so it's worth diagnosing before rebuilding anything.
Cause 1: The metrics were never defined
Symptom: two dashboards show different revenue numbers, and both are "right" by their own logic. One counts bookings, one counts invoiced revenue; one includes refunds, one doesn't. Nobody wrote down which definition is canonical, so every dashboard embeds its author's assumption.
Once a leader sees two conflicting numbers, they stop trusting both (rationally). From then on they ask an analyst, because the analyst can explain the number and a dashboard can't.
The fix isn't visual. It's a metrics layer: each metric defined once (i.e., in dbt or your semantic layer), version-controlled, tested & documented, with every dashboard reading from the same definition. This is transformation work, and skipping it is why the second BI rollout fails the same way the first one did.
Cause 2: The data underneath isn't trusted
Symptom: the dashboard was correct at launch, then a pipeline silently broke, and for two weeks it showed stale numbers before anyone noticed. One or two incidents like that and the team permanently downgrades the dashboard to "directionally interesting" and goes back to asking for pulls.
Trust in a report takes months to build and one incident to lose, and teams rarely re-adopt a dashboard they've caught being wrong. The fix is plumbing: freshness monitoring, data tests that fail loudly, an alert channel someone owns, and a visible "data as of" stamp so staleness is at least visible. If the underlying platform is the real constraint, that's a modernization conversation, but monitoring alone fixes more trust problems than replatforming does.
Cause 3: The dashboards answer questions nobody asks
Symptom: the dashboard has 40 charts, was built from "what's in the data," and answers everything except the question the VP has on Tuesday morning.
Dashboards get built forward from the schema (here are the columns, here's a chart for each) when they should be built backward from decisions. The method we use:
- List the decisions. For each intended audience: what do they decide weekly or monthly? (e.g., pricing, hiring pace, campaign budget, inventory buys).
- Map each decision to the 2–3 metrics that inform it. Not every metric that's related; the ones that would change the decision.
- Write the definition of each metric before charting it (see Cause 1).
- Build the smallest surface that covers the list. Usually this is 3–5 focused dashboards rather than 30, and every chart has to name the decision it serves.
A useful audit question for any existing chart: "what would we do differently if this number moved 20%?" If nobody can answer, cut the chart.
Which one do you have?
A quick self-diagnosis:
- Conflicting numbers across reports, arguments about whose figure is right → Cause 1, fix the metric definitions first.
- "The dashboard is wrong/stale" said from memory of a past incident → Cause 2, fix monitoring and rebuild trust deliberately.
- Dashboards are accurate and fresh but meetings still run on exported screenshots and ad-hoc pulls → Cause 3, rebuild backward from decisions.
Most real situations are a blend, but one cause usually dominates, and fixing the wrong one first is how companies end up on their third BI tool with the same complaints (a tool switch changes the look, not the causes).
If you want a second opinion before committing budget, describe your setup in a few sentences: which tool, how many dashboards, and what leaders complain about. We'll tell you which cause it sounds like and whether it's worth an engagement or just a pointed internal fix.