The Weekly Ops Review Is a Slide Deck Because Power BI Wasn’t Invited

Power BI is certified. The ops page refreshes overnight. The plant, the warehouse, and the service queue are in the model.

The weekly ops review still opens a slide deck.

Someone spent Monday building it. Someone else spent Tuesday reconciling it. Wednesday’s meeting walks the slides. The live page is a research tool for the person who made the pack.

If the review is still a deck, the model is a side channel. You can stop calling it the source.

The artifact is the operating system

This is not the whole management cadence: Power BI is live, the cadence never changed. Not screenshot culture: ask the model, don’t screenshot. Not the huddle going back to Excel: ops still runs the plant from spreadsheets. Not the printout at stand-up: why the plant manager prints the dashboard.

This is the staff meeting. It has an agenda, an owner, and a dated file. The company treats that file as the official hour.

A deck is a speech. A live page is a shared fact. The review can use both. It cannot pretend they are the same product. When the deck carries the actuals, Power BI was not invited. It was used backstage.

The deck is how they control the story: locked filters, commentary beside the tile, a VP who can present without clicking. Real needs. Also how a certified model becomes a paste source.

The test is simple. If the meeting could run without opening Power BI, Power BI is not the review. It is the kitchen.

The costs of running ops from a deck

1. The file becomes the source of truth. The model can be right and still lose. The room argues the slide. The slide was exported Monday night. Wednesday’s exception is missing or hand-typed. You did not have a review of operations. You had a review of a document.

2. Prep time is the hidden tax. Building the pack is a job. Checking last week’s numbers against this week’s extract is a job. Formatting the “what we will say” column is a job. None of that is a decision. It is how the meeting protects itself from the live product.

3. Accountability attaches to the presenter. When the number lives in a personal deck, the room asks who built it. When the number lives in a named measure, the room can ask who owns the result. A weekly ops review that still runs on authorship will never graduate to ownership.

4. Follow-ups leave as homework. “Which customers?” “Which lines?” “Is freight in this?” The live page could answer some of those in the room. The deck cannot. So the question becomes an email, then a new slide, then next week. Decision latency is the product of the artifact.

5. Exceptions get narrated instead of queried. A slide can highlight a red box. It cannot change the grain when the plant manager asks for the other shift. The review becomes a speech about last week’s exceptions. It stops being a tool for this week’s choice.

6. Usage looks healthy and still fails. The analyst opens the page every Monday. Nobody opens the dashboard is not this pattern. This is worse: one person opens it so the rest of the room never has to.

7. The deck never dies. “Just for this quarter” becomes the standing pack. New slides accrete. Old slides stay because someone might ask. The live page cannot compete with a ritual that already has a slot on the calendar.

The old review can absorb a new tool without changing at all. That is the point. A technically successful Power BI launch can still leave Wednesday owned by PowerPoint.

How to invite the live page—or stop calling it the source

1. Put the governed page on the agenda by name. First item. Not “pre-read.” Not “appendix.” The review opens the same certified ops view every week. If that sentence is uncomfortable, you already know the deck is the real product.

2. Name the decisions the hour owns. Capacity moves. Overtime. Expedites. Service recovery. Inventory pulls. If the meeting only “reviews performance,” it will consume charts and produce commentary. A decision creates an information requirement the live page can meet.

3. Freeze only what must be frozen. A dated as-of is legitimate. A statutory snapshot is legitimate. A 40-slide reconstruction of numbers the model already has is not. Stamp the time. Open the page. Stop pasting actuals into shapes.

4. Rewrite the hour around exceptions. Do not walk every tile. Start with what crossed a threshold, what changed since last week, and what requires a choice. Power BI should shorten the review. Digitizing the old tour of slides is how you get a slower meeting with nicer colors.

5. Keep slides for narrative, not for actuals. Strategy, a customer story, a safety brief, a decision log—those can stay in a deck. Shared measures cannot. Two official artifacts means neither is official. If a number is in both, the deck will win, because the presenter controls it.

6. Put the owner beside the measure. Every exception needs a business owner. The model steward owns meaning. The operational leader owns the result. The person who used to build the pack is not the owner of throughput.

7. Answer the next cut from the model. When the room asks “which lines,” go to the governed dimension in the meeting. If the model cannot answer, write the gap down. Do not create a private extract that becomes next week’s slide. Recurring questions belong in the product: standing questions should not be ad-hoc.

8. Cap prep. If the pack still takes a day, the page is wrong or the ritual is wrong. Fix grain, thresholds, and the agenda. Do not hire more time to feed a side channel.

9. Review the artifact after four cycles. Did slide count fall? Did actuals leave the deck? Did follow-ups stay on the trusted model? Do not call this adoption because logins rose. Look at Wednesday.

What a live ops review looks like

The meeting opens the same governed view. The as-of is on the page. Leaders do not bring private actuals.

Commentary still exists. Someone still says what they will do by Friday. The deck, if it survives, is thin: decisions, owners, due dates. Not a second ledger in widescreen.

The chair enforces the rule. “Where is that number?” is a live-page question. A paste from Monday is not an answer.

Executive takeaway

A weekly ops review that still runs on slides has not adopted Power BI. It has hired Power BI as a research assistant for the deck.

Put the live page on the agenda. Keep slides for narrative. Move actuals back to the model. If the meeting cannot survive that, stop calling the model the source.

Need a 30-minute look at whether Wednesday still runs on a deck? Contact Alluvium. We’ll map one ops review, the artifact that owns it, and the live page that should take the actuals.