Why your dashboards keep multiplying

It starts with one good reason

Someone in sales asks how many accounts churned last quarter without a warning sign. An analyst writes the query, it is useful, and the natural thing to do is save it somewhere everyone can see. A dashboard is born.

Three weeks later the same question arrives with a filter on it. Rather than argue about the filter, the analyst clones the dashboard. That is the whole mechanism. No one decided to have forty of them.

The cost is not the dashboards

A dashboard is cheap to build and expensive to trust. Each one carries a definition of a metric, and those definitions drift apart the moment two people edit two copies. By the time anyone notices, three teams are quoting three different churn numbers in the same meeting.

The fix is not a tidier dashboard library. It is making the question cheaper to ask than the dashboard is to clone.

Ask, do not build

When an answer takes forty seconds and cites the tables it used, nobody needs to save it. They ask again next quarter, and the number comes from the same definitions as last time, because the definitions live in one place.