Which Power BI Operating Model Are You Actually Running? (A 6-Question Diagnostic)

The Headache

Picture the quarterly business review. The CFO walks through the deck, lands on the revenue slide, and the COO (who presented thirty minutes earlier) stares at the screen and says, “That’s not the number I had.”

Both of them pulled from “the dashboard.” Both of them used “the official” data. Neither of them is lying. By Thursday, IT will be asked to put in writing why finance and operations cannot agree on a single quarter’s revenue. This is the kind of email that ages people.

The thing is, Power BI did not fail. Fabric did not fail. The semantic models did exactly what they were configured to do, which is the problem. What failed was the operating model, the unspoken agreement about who owns what, who can build what, and which numbers carry organizational weight.

Most mid-market organizations have never actually decided. They have drifted. Somewhere between the IT director who locked everything down in 2019 and the FP&A analyst who taught herself DAX during lockdown, an accidental operating model emerged. It works fine until the board meeting. Then it doesn’t.

This is the first issue in a three-part series on the Power BI operating model.Before we talk about what to do, we have to be honest about where you actually are.

The Blueprint: A 6-Question Diagnostic

Forget the architecture diagrams for a moment. Most of them are gorgeous and most of them have nothing to do with what your organization is actually doing on a Tuesday morning. Here is how to diagnose your real operating model. Answer honestly. Nobody is grading this.

1. When a business user wants a new report, where do they start?

Centralized:They file a ticket with IT or the BI team, then wait.

Self-service:They open Power BI Desktop and connect to whatever source they can find.

Hybrid (functional):They open Power BI Desktop and connect to a certified semantic model.

The difference between functional hybrid and self-service chaos is whether the starting pointis a governed model or a raw source. Same tool, completely different outcome.

2. How many semantic models do you have for the same business entity?

Search your tenant for “Sales,” “Revenue,” or “Customer.” If you find one certified model and a handful of personal models built on top of it, you are functionally hybrid. If you find seventeen models with overlapping logic and no clear winner, you are running uncoordinated self-service and calling it hybrid. The second category is more common than anyone admits in vendor case studies.

3. Who is actually authorized to apply the Certified endorsement?

Power BI distinguishes between Promoted (anyone with workspace write access can apply the blue badge) and Certified (only administrator-designated reviewers can apply the gold badge). If no one in your organization is authorized to certify, the endorsement framework is decorative. If everyone is authorized, it is meaningless. Functional hybrid requires a small, named group of certifiers, typically two to four people at a mid-market organization. If your answer is “I think Dave can do it? Maybe?” then your answer is you don’t know.

4. What happens when a certified semantic model changes?

If the answer is “the BI team emails affected report owners,” you have a coordination model. If the answer is “we don’t know who’s built on top of it,” you have a forthcoming incident. Lineage view in the Fabric portal is the diagnostic. Open it, pick your most important model, and count downstream dependencies. If you cannot name the report owners, your operating model has a gap that is going to find you eventually.

5. Where do business-built reports live?

Centralized:They don’t exist; IT builds everything (and the queue is six weeks long).

Self-service:They live in personal workspaces and OneDrive folders that nobody can find when the author leaves.

Hybrid:They live in domain-aligned workspaces with a domain admin who is not the same person as the report author.

Fabric domains, now generally available with delegated governance, are the structural feature that makes this work. If you are not using domains, you are running hybrid on willpower and good intentions, which are finite resources.

6. When a report breaks at 9 AM Monday, who fields the call?

The answer reveals more than any governance document. In a functional hybrid, the answer is layered: the business user owns the report logic, the central team owns the model, and there is a written agreement about which failure modes belong to which team. In a broken hybrid, the answer is “whoever picks up first,” which usually means the person who looks most senior on the email chain.

The Gotcha

Most organizations score themselves as hybrid because hybrid is the right answer in every Microsoft adoption deck, and nobody wants to be the person who scored their own org poorly. The diagnostic above usually reveals one of two failure modes. Centralized-with-shadow-IT, where the official model is locked down and finance is quietly running everything in Excel anyway. Or self-service-with-decorative-governance, where the endorsement badges exist but nobody enforces them and certification is something that happened once in 2022. Both call themselves hybrid. Neither is.

The Reddit Reality Check

A recent r/PowerBI thread, lightly paraphrased: an analyst’s leadership wants to “democratize data,” but every time a business user builds a report, finance disputes the numbers and IT gets blamed. The analyst asks how to “make governance work without killing self-service.”

The reality: governance and self-service are not in tension when the governed layer is the semantic model, not the report. The standard answer (certified semantic model in a central workspace, Live Connection from business-built reports) is correct, but it only works if the certified model genuinely covers the metrics the business needs. The most common cause of “shadow finance Excel” is that the certified model is missing the measure finance actually uses for revenue. So finance recreates it locally, the two numbers drift, and everyone blames the tool. Audit the certified model against the metrics that show up in board materials. If the metrics aren’t in the model, the model is not actually certified for the use case it’s being blamed for. It’s certified for a use case nobody is using.

What We’re Watching

Domain-level default sensitivity labels in Fabric went generally available earlier this year, which means new items in a workspace automatically inherit the domain’s label. For organizations where data classification has historically been a “someone should do this” agenda item that has lived on the same slide for four quarters, this is a quiet but significant governance lever. It pushes labeling out of human discretion and into the platform itself. Worth a look in your next admin portal review.

One Question for the Comments

When you ran the diagnostic above, which question was the most uncomfortable to answer honestly?

The Strategist’s Corner

If question four or question six made you wince, that is usually the symptom of an operating model that grew rather than one that was designed. We help mid-market organizations map their current Power BI operating model against where it needs to be. Typically a 90-minute session that produces a one-page diagnostic and three concrete next steps, all of which are cheaper than the post-board-meeting cleanup. Book a 30-minute scoping call →

Issue Two will cover what functional hybrid actually requires of the central team and the business: the operating agreements, the certification process, and the workspace structure that holds it all together.

Measure Twice. #1: Originally Posted on LinkedIn, June 10, 2026