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

Power BI is certified. The ops page refreshes overnight, and the plant, the warehouse, and the service queue are all in the model. The weekly ops review still opens a slide deck.

Someone spent Monday building it and someone else spent Tuesday reconciling it. Wednesday’s meeting walks the slides, and 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, and you can stop calling it the source.

The artifact is the operating system

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

This is the staff meeting. It has an agenda, an owner, and a dated file, and 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, but 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 presenters control the story: locked filters, commentary beside the tile, and a VP who can present without clicking. Those are real needs. They are also how a certified model turns into 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, because the room argues the slide. The slide was exported Monday night, so Wednesday’s exception is missing or hand-typed. You did not review operations. You reviewed 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 it lives in a named measure, the room can ask who owns the result. A 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, and the deck cannot. So the question becomes an email, then a new slide, then next week. Decision latency is a product of the artifact.

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

6. Usage looks healthy and still fails. The analyst opens the page every Monday. This is not the nobody opens the dashboard pattern. It 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 and 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, and 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. Make it the first item, not a pre-read or an appendix. The review opens the same certified ops view every week. If that sentence makes you 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, and so is a statutory snapshot. A 40-slide reconstruction of numbers the model already has is not. Stamp the time, open the page, and 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 slide tour just gets you a slower meeting with nicer colors.

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

6. Put the owner beside the measure. Every exception needs a business owner. The model steward owns the meaning and the operational leader owns the result. The person who used to build the pack does not own 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 instead of creating a private extract that becomes next week’s slide. Recurring questions belong in the product, as in standing questions should not be ad-hoc.

8. Cap prep. If the pack still takes a day, either the page or the ritual is wrong. Fix the grain, thresholds, and 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 it adoption because logins rose. Look at Wednesday.

What a live ops review looks like

The meeting opens the same governed view with the as-of on the page, and leaders do not bring private actuals.

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

The chair enforces the rule. “Where is that number?” is a live-page question, and 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, and move actuals back to the model. If the meeting cannot survive that, stop calling the model the source.

Want to know whether Wednesday still runs on a deck? Book a session with Alluvium. We will map one ops review, the artifact that owns it, and the live page that should carry the actuals. To check the model behind that page, request a free Model Health check.