Introduction & The Chaos HookPower BI. The golden promise of self-service analytics—and the silent destroyer of data consistency. Everyone loves it until you realize your company has forty versions of the same “Sales Dashboard,” each claiming to be the truth. You laugh; I can hear it. But you know it’s true. It starts with one “quick insight,” and next thing you know, the marketing intern’s spreadsheet is driving executive decisions. Congratulations—you’ve built a decentralized empire of contradiction.Now, let me clarify why you’re here. You’re not learning how to use Power BI. You already know that part. You’re learning how to plan it—how to architect control into creativity, governance into flexibility, and confidence into chaos.Today, we’ll dismantle the “Wild West” of duplication that most businesses mistake for agility, and we’ll replace it with the only sustainable model: the Hub and Spoke architecture. Yes, the adults finally enter the room.Defining the Power BI ‘Wild West’ (The Problem of Duplication)Picture this: every department in your company builds its own report. Finance has “revenue.” Sales has “revenue.” Operations, apparently, also has “revenue.” Same word. Three definitions. None agree. And when executives ask, “What’s our revenue this quarter?” five people give six numbers. It’s not incompetence—it’s entropy disguised as empowerment.The problem is that Power BI makes it too easy to build fast. The moment someone can connect an Excel file, they’re suddenly a “data modeler.” They save to OneDrive, share links, and before you can say “version control,” you have dashboards breeding like rabbits. And because everyone thinks their version is “the good one,” no one consolidates. No one even remembers which measure came first.In the short term, this seems empowering. Analysts feel productive. Managers get their charts. But over time, you stop trusting the numbers. Meetings devolve into crime scenes—everyone’s examining conflicting evidence. The CFO swears the trend line shows growth. The Head of Sales insists it’s decline. They’re both right, because their data slices come from different refreshes, filters, or strangely named tables like “data_final_v3_fix_fixed.”That’s the hidden cost of duplication: every report becomes technically correct within its own microcosm, but the organization loses a single version of truth. Suddenly, your self-service environment isn’t data-driven—it’s faith-based. And faith, while inspirational, isn’t great for auditing.Duplication also kills scalability. You can’t optimize refresh schedules when twenty similar models hammer the same database. Performance tanks, gateways crash, and somewhere an IT engineer silently resigns. This chaos doesn’t happen because anyone’s lazy—it happens because nobody planned ownership, certification, or lineage. The tools outgrew the governance.And Microsoft’s convenience doesn’t help. “My Workspace” might as well be renamed “My Dumpster of Unmonitored Reports.” When every user operates in isolation, the organization becomes a collection of private data islands. You get faster answers in the beginning, but slower decisions in the end. That contradiction is the pattern of every Power BI environment gone rogue.So, what’s the fix? Not more rules. Not less freedom. The fix is structure—specifically, a structure that separates stability from experimentation without killing either. Enter the Hub and Spoke model.Introducing Hub and Spoke Architecture: The Core ConceptThe Hub and Spoke design is not a metaphor; it’s an organizational necessity. Picture Power BI as a city. The Hub is your city center—the infrastructure, utilities, and laws that make life bearable. The Spokes are neighborhoods: creative, adaptive, sometimes noisy, but connected by design. Without the hub, the neighborhoods descend into chaos; without the spokes, the city stagnates.In Power BI terms:* The Hub holds your certified semantic models, shared datasets, and standardized measures—the “official truth.”* The Spokes are your departmental workspaces—Sales, Finance, HR—built for exploration, local customization, and quick iteration. They consume from the hub but don’t redefine it.This model enforces a beautiful kind of discipline. Everyone still moves fast, but they move along defined lanes. When Finance builds a dashboard, it references the certified financial dataset. When Sales creates a pipeline tracker, it uses the same “revenue” definition as Finance. No debates, no duplicates, just different views of a shared reality.Planning a Hub and Spoke isn’t glamorous—it’s maintenance of intellectual hygiene. You define data ownership by domain: who maintains the Sales model? Who validates the HR metrics? Each certified dataset should have both a business and technical owner—one ensures the measure’s logic is sound; the other ensures it actually refreshes.Then there’s life cycle discipline—Dev, Test, Prod. Shocking, I know: governance means using environments. Development happens in the Spoke. Testing happens in a controlled workspace. Production gets only certified artifacts. This simple progression eliminates midnight heroics where someone publishes “final_dashboard_NEW2” minutes before the board meeting.The genius of Hub and Spoke is that it balances agility with reliability. Departments get their self-service, but it’s anchored in enterprise trust. IT keeps oversight without becoming a bottleneck. Analysts innovate without reinventing KPIs every week. The chaos isn’t eliminated—it’s domesticated.From this foundation, true enterprise analytics is possible: consistent performance, predictable refreshes, and metrics everyone can actually agree on. And yes, that’s rarer than it should be.The Hub: Mastering Shared Datasets and Data GovernanceLet’s get serious for a moment because this is where most organizations fail—spectacularly. The Hub isn’t a Power BI workspace. It’s a philosophy wrapped in a folder. It defines who owns reality. When people ask, “Where do I get the official revenue number?”—the answer should never be “depends who you ask.” It should be, “The Certified Finance Model in the Hub.” One place, one truth, one dataset to rule them all.A shared dataset is basically your organization’s bloodstream. It carries clean, standardized data from the source to every report that consumes it. But unlike human blood, this dataset doesn’t circulate automatically—you have to control its flow. The minute one rogue analyst starts building direct connections to the underlying database in their own workspace, your bloodstream develops a clot. And clots, in both analytics and biology, cause strokes.So the golden rule: the Hub produces; the Spokes consume. That means every certified model—your Finance Model, your HR Model, your Sales Performance Model—lives in the Hub. The Spokes only connect to them. No copy–paste imports. No “local tweaks to fix it temporarily.” If you need a tweak, propose it back to the owner. Because the Hub is not a museum; it’s a living system. It evolves, but deliberately.Now, governance begins with ownership. Every shared dataset must have two parents: a business owner and a technical one. The business owner decides what the measure means—what qualifies as “active customer” or “gross margin.” The technical owner ensures the model actually functions—refresh schedules, DAX performance, gateway reliability. Both names should be right there in the dataset description. Because when that refresh fails at 2 a.m. or the CFO challenges a number at 9 a.m., you shouldn’t need a company-wide scavenger hunt to find who’s responsible.Documenting the Hub sounds trivial until you realize memory is the least reliable form of governance. In the Hub, every dataset deserves a README—short, human-readable, and painfully clear. What are the data sources? What’s the refresh frequency? Which reports depend on it? You’re not writing literature—you’re preventing archaeology. Without documentation, every analyst becomes Indiana Jones, digging through measure definitions that nobody’s updated since 2022.Then there’s certification. Power BI gives you two signals: Promoted and Certified. Promoted means, “Someone thinks this is good.” Certified means, “The data governance board has checked it, blessed it, and you may trust your career to it.” In the Hub, Certification isn’t decorative; it’s contractual. The Certified status tells every other department: use this, not your homegrown version hiding in OneDrive. Certification also comes with accountability—if the logic changes, there’s a change log. You don’t silently swap a measure definition because someone panicked before a meeting.Lineage isn’t optional either. A proper Hub uses lineage view like a detective uses fingerprints. Every dataset connects visibly to its sources and all downstream reports. When your CTO asks, “If we deprecate that SQL table, what breaks?” you should have an instant answer. Not a hunch. Not a guess. A lineage map that shows exactly which reports cry for help the moment you pull the plug. The hub turns cross-department dependency from mystery into math.Version control comes next. No, Power BI isn’t Git, but you can treat it as code. Export PBIP files. Store them in a repo. Tag releases. When analysts break something—because they will—you can roll back to stability instead of reengineering from memory. Governance without version control is like driving without seatbelts and insisting your reflexes are enough.Capacity planning also lives at the hub level. Shared datasets run on capacity; capacity costs money. You don’t put test models or one-off prototypes there. The Hub is production-grade only: optimized models, incremental refresh, compressed columns, the works. Every refresh must be scheduled deliberately to avoid collision. Refreshing fifteen models at 8 a.m. is not governance—it’s CPU arson.Now, let’s address the political side. Governance means saying no—strategically, calmly, and repeatedly. When a manager in

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

If this clashes with how you’ve seen it play out, I’m always curious. I use LinkedIn for the back-and-forth.