Stop Commissioning a New Dashboard for Every Question

A new page for every question is how you get sprawl. It feels like service. It is demand with no intake.

Mid-market leaders get a Slack ping, a hallway ask, a board follow-up. Someone commissions a dashboard. A week later there is another pbix. The original question was one filter on a model you already had—or should have had. You funded a brochure. You underfunded the product.

This is intake, not the cleanup of last year’s files

Dashboard sprawl is a tax is the estate you already have: inventory, certify, retire. This piece is how the next file gets born. Demand management. Who is allowed to turn a question into a build.

If you only retire, the hose is still on. If you only freeze publishing, questions move to email. You installed a backlog in the inbox.

The search is real: “too many dashboard requests,” “Power BI intake process.” People are not asking for a portal. They are asking how to stop saying yes to a page every time a VP is curious.

From dashboards to decisions is the strategy test: is this even a decision. This post is the operating rule after that test. Recurring questions hit the model. One-offs do not get a workspace.

How a question becomes a file

Someone needs a cut. Region. Product line. A week. The certified app does not have that slicer—or nobody looked. A builder copies a report. They publish. The question is answered once.

Next month the question returns with a different week. The copy is stale. Another copy. Now you have three brochures and one unanswered product need: a dimension and a measure with an owner.

Self-service was supposed to be explore-on-the-model. Commissioning a dashboard is explore-by-fork. Forks are how every team builds their own model when the ask is big, and how sprawl returns when the ask is small.

IT feels this as a ticket queue: the hidden cost of waiting on IT. The wait is real. So is the reflex to skip the queue by standing up a side file. Both are intake failures.

What a page-per-question policy costs

1. You pay for answers that cannot be reused. A one-off page does not accumulate. The next similar question starts at zero. The model would have compounded. The brochure does not.

2. Builders never get to the product. Every sprint is a new canvas. Grain never freezes. The semantic model is the product. If funding follows pages, the product starves. You will rebuild the same report every quarter.

3. The official app gets quieter. Leadership cannot find the number because the last answer lived in a side workspace named after a person. Adoption falls. They commission another page. The loop feeds itself.

4. No one can say no, so nothing is done. A program without a cut is a queue: analytics programs fail in delivery. Each yes is polite. The certified measure slips a month.

5. Questions that should be ad-hoc become assets. A board follow-up is not a product. Treating it like one creates a report that must refresh forever. Capacity groans. Ghosts accumulate. Then you buy headroom instead of a rule.

6. Finance inherits twins they will not sign. Extra pages drift extra filters. The controller sees a total that does not tie. They refuse the whole app. Sign-off is a feature. Intake that bypasses the steward is how you earn that refusal.

What not to do

Do not stand up a request portal that still ships a dashboard for every ticket. A form is not a policy. The policy is: model first, page only if the question is recurring and owned.

Do not make executives wait two months to slice a certified model. That is how they commission a rebel file. Self-service on the official model is the release valve. Self-service as a new dataset is the leak.

Do not inventory as a substitute for intake. Cleaning last year’s mess without a “how work enters” rule is a one-time hero project.

Do not measure the BI team on tickets closed. Measure them on certified measures in use, and on requests that were answered without a new file.

How to fund the model and starve the one-off page

1. Install one intake path. All asks hit the same backlog. Requester, decision, whether it already exists on the model, whether it is recurring. Shadow commissions are how sprawl returns. If a VP can spin a workspace without that card, you do not have a program. You have a suggestion box with licenses.

2. Triage in three buckets, out loud. Already in the app—train, bookmark, stop. Model change—new grain, new measure, new dimension, with a steward. Working paper—Excel or a sandbox connected to the model, no official stamp, no 6 a.m. SLA. Most hallway questions are bucket one or three. They die as pages when you say that.

3. Answer from the model before you open Desktop. Can a filter, a field, or a measure on the certified semantic model settle it. If yes, do that. Publish nothing new. Ask the model instead of screenshotting a one-off. If the model cannot answer because grain is wrong, that is a product backlog item, not a canvas.

4. Require a steward for anything that will refresh twice. A page that must live needs an owner who can freeze the definition. No steward, no schedule. That rule alone kills vanity dashboards. It is the same ownership split as a project with no owner.

5. Time-box one-offs and refuse to promote them by default. A sandbox report can exist for a board cycle. Then it expires. Promotion to the app is a decision: recurring, signed, tied. The first ninety days should prove this loop in one domain before you scale intake theater.

6. Review demand like a PMO, not like a help desk. Rank against the P&L. Cut. Publish the no’s. Change leadership is part of the work: data project management. If the backlog is only pages, rewrite it as products. Strategy without a cut needs a roadmap that names decisions, not a longer wish list.

Start where the hose is worst. One VP. One standing meeting. Prove that questions can die as filters.

What good looks like

The ELT still asks sharp questions. They get answers from the app the same day, or they get a dated working paper, or they get a date for a model change. They do not get a new workspace by default.

Builders spend more time on grain than on themes.

The certified set stays short. Sandboxes are labeled. Expiration is real.

When sprawl creeps back, you have a retire list and an intake rule. Cleanup without demand management is a season. Intake is the climate.

[Judgment:] if your backlog is a list of dashboards, you are taking orders. If it is a list of model changes and refusals, you are running a program.

Frequently asked questions

Won’t this slow us down? It slows the first yes. It speeds the tenth question.

What do we do with true one-offs? Answer them. In Excel connected to the model, or in a sandbox with an expiry. Do not put them on the 6 a.m. refresh that the close depends on.

How is this different from dashboard sprawl? Sprawl is inventory you already have. This is the tap. Retire without intake and you will write that post again next year.

Get started

Fund the model. Put every ask through one intake. Answer from the product you already paid for.

Need a 30-minute look at which requests should never become a file? Contact Alluvium. We’ll sort the backlog into model, working paper, and no—not another page.

Book a 30-minute consult.