The visible 10% and the invisible 90%
Building the chart is genuinely fast with modern BI tools. What takes the actual time is locating a trustworthy source for the underlying metric, resolving disagreements about its exact definition across teams, and building a pipeline resilient enough that the dashboard doesn't silently go stale.
A request that looks like 'one dashboard' is frequently, underneath, 'define this metric for the first time, for the whole company' — a much bigger and more valuable piece of work, if named correctly.
Metric definition debt compounds quietly
Without a shared metric registry, the same business term — 'active user', 'churn', 'revenue' — gets defined slightly differently by every team that needs it, and each new dashboard adds one more inconsistent definition to reconcile later.
This debt is invisible until two dashboards disagree in front of an executive, at which point the cost of resolving it retroactively is far higher than defining it once, up front, would have been.
Reframing the request
Treat every dashboard request as two separable asks: does this metric already have an agreed, owned definition, and does the data behind it need a new pipeline. Answering both honestly, up front, turns a vague scope argument into a concrete, estimable project — and often reveals that the valuable deliverable is the metric definition, not the chart.
This reframe tends to make stakeholders more patient, not less, because it shows them exactly where the real effort and value actually sit.
Nobody asks for a metric definition. Everybody asks for a dashboard. The dashboard is just where the missing definition becomes visible.MNB Data Practice
Key actions
- Separate 'does this metric have an agreed definition' from 'build the chart'
- Maintain a shared, owned metric registry
- Name the pipeline work explicitly in the estimate, not just the visualisation
- Resolve metric disagreements before they reach an executive dashboard