The First 90 Days of a Power BI Program

Ninety days is enough to prove a reporting loop. It is not enough to boil the company.

A mid-market program that spends the quarter on a roadmap slide has already failed the only test that matters: did one meeting start using one trusted number. One model. One app. One owner. Everything else is a sequel.

The quarter is a loop, not a museum of pages

Leaders search “Power BI 90 day plan” after a kickoff that felt expensive. They were promised a platform. They got a backlog of dashboards and a steering color.

The right first quarter does not ship a catalog. It ships a loop: source to model to app to meeting to steward. Then it repeats. That is delivery, not a tool upgrade. We already said programs fail in delivery, not in the stack. This piece is the calendar.

Do not confuse this with a proof-of-value slide for a later pitch. This is operating work. If day ninety still points at “phase two,” you ran a workshop. You did not run a program.

The three objects that must exist:

One semantic model. Grain named. Measures named. Refresh owned. The model is the product. The reports can wait to be pretty.

One app. The place the ELT actually opens. Not twelve workspaces. Not a SharePoint scavenger hunt.

One owner. A person who can cut scope and freeze a definition. Hosting is not owning: why the project has no owner.

If you cannot staff those three, do not start a “program.” Start a smaller loop in one domain and tell the truth about it.

What a slide-first ninety days costs

1. The close does not move. You designed a future estate. Finance still pastes. Month-end still takes a week. The quarter was theater. The P&L did not notice.

2. Every VP adds a page. Without a cut, the backlog is a suggestion box. The team is busy. Nothing certified ships. Busy is not a KPI. Intake without a no is how you commission a dashboard per question.

3. Steering hears architecture, not a meeting change. Green on “model in progress” is not control. Control is: this measure is signed, this pack is live, this twin is retired. If Monday still starts with email, the status was decoration.

4. Change is scheduled for after go-live. Users keep the workbook. You declared a deploy. The operating cadence did not move. Change work belongs in week one: data project management and change leadership.

5. You buy platform before product. Capacity, a lake, another license batch. None of that creates the loop. Capacity is not a strategy. The first quarter should starve extras until one app is used.

6. Trust never gets a chance. A demo with sample data trains the room to ignore the next link. The second ninety days starts underwater.

What not to do

Do not inventory the whole company before you certify one domain. Catalogs without a live pack become another report.

Do not staff a center of excellence as a substitute for a steward. A CoE without a ship date is a committee.

Do not measure the quarter by report count. Measure by one signed measure in one meeting, and the old file gone.

Do not wait for perfect source data. Pick a grain finance will sign with the dirt that exists, then tighten. Waiting for a pristine lake is how the quarter ends empty.

The ninety-day plan: one model, one app, one owner

1. Days 1–15: pick the decision and name the three seats. Which meeting. Which number. Controller or plant VP as consumer. Steward who can freeze grain. Operations owner for refresh. Write it down. If two domains are “equally urgent,” pick the one that already argues every Monday. Strategy without a named decision is dashboards without decisions.

2. Days 1–30: freeze grain and a short measure list. Revenue. Margin. Inventory. On-time. Whatever that meeting actually fights about. Not forty KPIs. A sentence per measure: include, exclude, grain, owner. Unexplained measures are not KPIs. Connect sources that already exist. Do not rebuild the ERP.

3. Days 20–45: stand up the model as a product, not a file. Relationships that match how the business ships and books. Refresh on a clock the close can live with. Access that matches who may see the plant. A failed 6 a.m. job is close risk, not a curiosity. Put refresh on the same board as build.

4. Days 30–60: one app, one pack, one retire list. The brochure can be ugly. It must be the pack. Point the meeting at it. Name the twins you will turn off. Do not launch a museum. If Excel is still the right place for scenarios, connect it—do not paste. The split is Excel vs Power BI, not a religion.

5. Days 45–75: run the meeting on the app. Sit in it. Capture every “that’s not my number.” That list is the backlog, ranked. Fix definitions. Do not add pages to dodge the argument. Finance sign-off is a feature: why finance won’t sign the dashboard. Treat refusal as a spec.

6. Days 60–90: lock the loop and cut the rest. Owner still named. Steward still answering. Old file gone or labeled working paper. Next quarter’s one addition ranked. Everything else waits. If you cannot say no at day ninety, you do not have a program. You have a queue.

Start in one domain. Finance close. Or one plant. Prove the loop. Then copy the method, not the pages.

What good looks like on day ninety

The ELT can say where the number lives without a hunt.

The steward can say what the measure includes in one sentence.

Refresh finished before the meeting that used it. At least once on a close week.

Someone lost the old workbook and did not get it back.

The next request hits a backlog, not a side file.

That is enough. A lakehouse can wait. A CoE handbook can wait. A second department can wait until the first loop is boring.

If day ninety is a slide of future dashboards, you spent the quarter on hope. Hope is not a reporting system.

Frequently asked questions

Can we do two domains in ninety days? Usually no. Two domains is two stewards, two grains, two meetings. That is how both stay half-done. Sequence them.

What if source data is dirty? Dirty data shows up as arguments, not a red X. You will hit that. Name the duplicates and late files. Do not pause the quarter for a tooling RFP. See data quality shows up as arguments.

Do we need a partner for ninety days? Only if you do not have someone who can own sequence, stakeholders, and the first freeze at the same time. A borrowed lead for a quarter is cheaper than a year of status.

Get started

Stop planning a platform. Fund one loop: one model, one app, one owner, ninety days.

Need a 30-minute look at what your first quarter should actually ship? Contact Alluvium. We’ll name the meeting, the measure, and the cut—not a roadmap of pages.

Book a 30-minute consult.