Skip to content
KadmoonBusiness Intelligence
Power BI5 min read

Running the weekly business review on Power BI

Why the recurring leadership meeting is where reporting either earns its keep or gets ignored, and how to run a weekly business review on Power BI so the meeting is about decisions, not about reconciling numbers.

Key takeaways

  • The recurring leadership meeting is where reporting proves its value, because it is where the numbers meet decisions regularly.
  • Running the review on one governed Power BI view stops the meeting from starting with reconciling whose numbers are right.
  • Tying reports to a standing meeting is one of the most effective ways to drive adoption, because the routine pulls people to the data.
  • A good review opens on the few things that matter and drills into them live when a question comes up.
  • The goal is a meeting about decisions and actions, not a meeting about assembling and arguing over data.

Every organization has the recurring leadership meeting: the weekly or monthly review where leaders look at how the business is doing and decide what to do about it. It is also, quietly, where reporting either earns its keep or gets ignored, because it is the moment the numbers meet decisions on a regular cadence. Most of these meetings are worse than they should be, starting with reconciling whose numbers are right and ending with questions parked for later. Running the review on Power BI changes that. Here is how, and why the meeting matters more to your reporting than you might think.

The meeting is where reporting proves itself

Start by recognizing what the recurring review actually is: the place where reporting and decisions meet, regularly. All the dashboards and reports in an organization are ultimately meant to inform decisions, and the standing leadership meeting is where a large share of the important decisions get made with the numbers in front of everyone. So the review is where reporting most directly proves its value, or fails to.

This makes the meeting a high-leverage place to get reporting right. If the review runs well on trusted data, the reporting is demonstrably driving decisions, every week, in front of the people who matter most. If the review is a mess of competing spreadsheets and unanswerable questions, the reporting is visibly failing at its job, also every week. The recurring meeting is both the best showcase for good reporting and the harshest exposure of bad reporting, which is why it is worth running on a proper foundation.

One governed view ends the reconciliation

The most common failure of the leadership review is that it starts with reconciling numbers. People arrive with their own spreadsheet exports, pulled at different times with different adjustments, and the first stretch of the meeting goes to arguing about whose pipeline or revenue figure is right, instead of deciding anything.

Running the review on one governed Power BI view removes this at the root. When everyone looks at the same governed model, there is one pipeline number, one revenue figure, one of everything, and they reconcile because they come from the same place. There is nothing to argue about, because there are not competing versions. The reconciliation that consumes the start of so many meetings simply does not happen, and the meeting can spend its time on what the numbers mean and what to do.

This alone transforms the meeting. A review that no longer burns its first portion on reconciling numbers is a review with time to actually decide things, which is what the meeting is for. And because the governed view is current, the numbers are up to date rather than being last week's export, so the decisions are made on the real current picture.

Running on live data, not slides

The traditional review runs on slides, a deck someone spends hours each week assembling by hand. This has two problems: the slides are a static snapshot, and the moment a question arises that the slides do not answer, the meeting stalls or the question gets parked for later. Both waste the meeting and the preparation.

Running the review on a live, governed Power BI view fixes both. There is no deck to assemble, so the hours spent each week building slides are recovered and the risk of the deck's numbers not matching someone's own pull disappears. And because the view is live and drillable, when a question comes up, this is down, why, where, you drill into it in the room and answer it, rather than deferring it. The meeting shifts from presenting a hand-built snapshot to working with live, trusted data that can answer its own questions.

This changes the character of the meeting. Instead of reciting a static deck and collecting questions to answer afterward, the review becomes an interactive working session where leadership explores the real data together and reaches decisions, with follow-up questions resolved live rather than parked. The meeting gets faster, more current, and more decisive, because it is working with data rather than with a snapshot of data.

The meeting drives adoption

There is a benefit to running the review on Power BI that reaches beyond the meeting itself: it is one of the most effective ways to drive adoption of the reporting. This matters because adoption is where reporting investments usually fall short, reports get built and then not used.

The reason is that a report which depends on people choosing to open it competes with everything else for attention and often loses. But a report that is the center of a standing weekly meeting gets used every week, because the meeting carries it. Tying the reporting to a recurring review builds the habit of using it into the organization's routine, which is far more reliable than hoping people adopt it on their own. The meeting pulls people to the data on a schedule, so the data gets used consistently rather than occasionally.

This is why connecting reports to routines is such a powerful adoption lever, and the leadership review is the most valuable routine to connect them to. The meeting is simultaneously a use of the reporting and the engine of its adoption: running it on Power BI both improves the meeting and ensures the reporting is used, week after week, by the people who most need it. Few single moves do more for whether an organization's reporting actually gets used.

A review about decisions

Pulling it together, running the weekly business review on Power BI produces a meeting that is about decisions rather than data assembly:

  • No reconciliation, because everyone shares one governed view where the numbers agree.
  • Live, not slides, so there is no deck to build and questions get answered in the room by drilling in.
  • Focused on what matters, opening on the few numbers that inform the decisions rather than reciting a full scorecard.
  • An adoption engine, because the standing meeting pulls people to the reporting every week and builds the habit of using it.

The goal is a meeting about decisions and actions, not about assembling and arguing over data, and running it on a governed Power BI view is what gets you there. The review stops being the weekly ritual of reconciling spreadsheets and reciting slides and becomes the working session where leadership makes decisions on current, trusted data, with questions answered live. That is a better meeting on its own terms, and it is also, quietly, one of the best things you can do to make sure your reporting is actually used. Get the recurring review right, and you improve both the meeting and the adoption of everything the reporting is for.

Frequently asked questions

Why run a business review on Power BI instead of slides?

Because slides are a snapshot assembled by hand, and the moment someone asks a question the slides cannot answer, the meeting stalls or defers. Running the review on a live, governed Power BI view means the numbers are current, consistent, and drillable: when a question comes up, you drill into it live and answer it in the room. It also removes the hours spent each week assembling the deck, and the risk of the deck's numbers not matching what someone else pulled. The meeting shifts from presenting a static, hand-built snapshot to working with live, trusted data, which makes it faster, more current, and able to answer its own questions.

How does a standing meeting help Power BI adoption?

It is one of the most effective adoption levers there is, because the routine pulls people to the data rather than relying on them to remember to look. A report that depends on people choosing to open it competes with everything else and often loses; a report that is the center of a standing weekly meeting gets used every week because the meeting carries it. Tying the reporting to a recurring review builds the habit of using it into the organization's routine, which is far more reliable than hoping people adopt it on their own. The meeting is both a use of the reporting and the thing that drives its adoption.

What makes a good Power BI business review?

It opens on the few things that matter, leads with the point rather than walking through every metric, and drills into questions live as they arise. The review should start from the decisions the leadership team needs to make and show the handful of numbers that inform them, with context, so the meeting focuses on what matters rather than reciting a full scorecard. When a number raises a question, the live governed view lets you drill into it in the room and answer it, so the meeting reaches decisions instead of parking questions for later. A good review is a decision-making session supported by live data, not a data-reading session.

Won't people still argue about the numbers?

Far less, because the numbers come from one governed source everyone shares, so there is nothing to argue about. The usual meeting argument, whose figure is right, happens because people arrive with different spreadsheet exports that diverged. When the review runs on one governed Power BI model, there is one pipeline number, one revenue figure, one of everything, and they reconcile because they come from the same place. That removes the reconciliation argument that consumes the start of so many meetings, and lets the meeting spend its time on what the numbers mean and what to do, which is the entire point of having the review.

Related resources

Have a project that fits this?

Tell us about it and you get a technical proposal within one business day, covering scope, architecture, timeline, and investment.

Start a project

Keep reading