November 3, 2025 • 24 mins
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 happ
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:00):
POWERBI, 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
interns spreadsheet is driving executive decisions. Congratulations, you've built a
(00:21):
decentralized empire of contradiction. Now let me clarify why you're here.
You're not learning how to use powerbi, 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.
Defining the power BI wild West, the problem of duplication.
Picture this. Every department in your company builds its own report.
(00:43):
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 an powerment. The
problem is that POWERBI makes it too easy to build fast.
(01:04):
The moment someone can connect an Excel file, they're suddenly
a data modeler. They save to one drive, 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
(01:24):
you stop trusting their numbers. Meetings devolve into crime scenes.
Everyone's examining conflicting evidence. The CFO swears the trend line
shows growth. The head of sales insists its decline. They're
both right because their data slices come from different refreshers, filters,
or strangely named tables like data final V three figx fixed.
That's the hidden cost of duplication. Every report becomes technically
correct within its own microcosm, but the organization loses a
(01:47):
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 have are the same.
Database performance tanks, gateways crash, and somewhere an IT engineer
silently resigns. This chaos doesn't happen because anyone's lazy. It
(02:09):
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
(02:30):
is the pattern of every power BIA 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, introducing hub and spoke architecture.
The 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
(02:52):
that make life bearable. The spokes are neighborhoods, creative, adaptive,
sometimes noisy, but connected by design. Without the hub, the
neighborhoods these into chaos. Without the spokes, the city stagnates.
In power bi terms, the hub holds your certified semantic models,
shared data sets, and standardized measures the official truth. The
spokes are your departmental workspaces. Sales, finance, HR build for exploration,
(03:16):
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 build a dashboard, it references the
certified financial data set. 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
(03:39):
a hub in spoke isn't glamorous. Its maintenance of intellectual hygiene.
You define data ownership by domain. Who maintains the sales model,
who validates the HR metrics. Each certified data set 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,
(04:01):
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 minutes before the board meeting. The genius of hubin
spoke is that it balances agility with reliability. Departments get
their self service, but it's anchored in enterprise trust. It
(04:23):
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
rareer than it should be. The Hub. Let's get serious
for a moment, because this is where most organizations fail spectacularly.
(04:45):
The Hub isn't a powerbi 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 data set to rule them all. A
shared data set is basically your organization's bloodstream. It carries clean,
(05:06):
standardized data from the source to every report that consumes it.
But unlike human blood, this data set 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
(05:30):
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 data set must have two parents,
(05:51):
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.
Refreshed schedules, DAX Performance Gateway reliability. Both names should be
right there in the data set description, because when that
refresh fails at two am or the CFO challenge is
a number at nine a M, you shouldn't need a
(06:12):
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 data set
deserves a read me, 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
(06:36):
definitions that nobody's updated since twenty twenty two. Then there's
certification POWERBI gives you two signals, promoted and certified. Promoted
means someone thinks this is good. Certified means the Data
Governance Board has checked it, blessed, 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,
(06:56):
not your homegrown version hiding in one drive. Certification also
comes with a cut ontability 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 data set connects visibly to its sources and all
downstream reports. When your CTO asks, if we deprecate that
(07:17):
sequel table, what breaks, you should have an instant answered,
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 POWERBI isn't GIT,
but you can treat it as code export PBIP files
store them in a repot tag releases. When analysts break something,
(07:38):
because they will, you can roll back to stability instead
of re engineering from memory. Governance without version control is
like driving without seat belts and insisting your reflexes are enough.
Capacity planning also lives at the hub level. Shared data
sets run on capacity. Capacity costs money. You don't put
test models or one of prototypes there. The hub is
production grade only optimized models, incremental refresh compressed columns the word.
(08:00):
Every refresh must be scheduled deliberately to avoid collision. Refreshing
fifteen models at eight am is not governance. It's CPU
arsen Now, let's address the political side. Governance means saying no, strategically, calmly,
and repeatedly. When a manager insists on adding a column
because they need it right now, the HUB team evaluates
it through impact, not emotion. How many reports depend on
(08:21):
this measure? Does it align with business definitions? Adding one
casual column might corrupt thirty downstream visuals? The Hub provides guardrails,
not customer service, but authority alone isn't enough. Visibility is
publish internal dashboards that track data set, health, refresh successes, failures,
refresh duration, data set size, number of connected reports. Let
(08:42):
leadership see governance in action. When executives visually witness uptime
at ninety nine percent, governance stops looking like red tape
and starts smelling like competence. Let's talk security. The Hub
enforces invisible discipline. That means row level security and object
level security are modeled here, not duct taped later by
the spokes. You define the filters one by region, division
or role, and every consuming report inherits them. No one copies,
(09:04):
ducks filters across ten workspaces like medieval scribes reproducing scripture.
Security is consistent inherited and auditible metadata. Hygiene rounds it out.
Sensitivity labels, and data loss prevention policies should originate in
the hub as defaults. Every certified data set carries its
classification like an ID badge, public, internal, confidential. When those
data sets flow into Excel or Outlook, the labels travel
(09:26):
with them. Governance isn't about blocking, It's about making trust portable. Finally, culture,
the hub is only as strong as the behavior it normalizes,
so institutionalized short show and tell sessions where departments present
improvements made to their reports or measures derived from Hub data.
Little rituals like that remind everyone that governance is collaboration,
not surveillance. The hub feeds the spokes, The spokes give
(09:49):
feedback to the hub. It's an ecological loop, not a monarchy.
When designed properly, the hub turns powerbi from a zoo
into a zoo with fences, feeding schedules, and a veterinarian.
The animals still roam, but nobody gets mauled. That is
shared governance done right. Predictable refreshes, defined ownership, certified semantics,
and a lineage so clear even auditors smile. That's the
(10:10):
infrastructure of trust you build before the chaos begins, and
once it exists, your spokes can finally innovate freely because
they know the hub has their back the spokes. Now
that the hub is keeping your data cleaned, certified, and
under control, it's time to talk about the parts everyone
actually sees the spokes. The spokes are where creativity lives,
where analysts experiment, and where business decisions happen at speed.
(10:33):
But freedom without structure is chaos. With better lighting, building
in the spoke means operating inside lanes that protect performance, consistency,
and user trust. A common temptation in the spokes is
to rebuild what's already in the hub. Duplicate measures, import
tables just in case, or tweak logic to match someone's
anecdotal truth. Don't. The purpose of the spoke is to
(10:54):
consume shared data, not reinterpret it. A thin report connects
life to certified data sets. It doesn't drag entire models
into memory. You're visualizing, not remodeling. Thinness is a virtue here,
fewer dependencies faster refreshes, lighter performance load. Think of each
spoke workspace as a showroom floor, elegantly displaying vehicles engineered
in the hub's factory. Optimization starts with model connections. Every
(11:16):
spoke should use live connections or direct links to semantic models,
not copies. That keeps data consistent and refreshed schedules centralized.
If someone insists on adding a localized measure, say a
region specific KPI, contain it within the report layer, documented
clearly as local logics so downstream users don't confuse it
with a certified field. Remember, traceability is oxygen. Without it,
(11:37):
creativity suffocates under ambiguity. Good spoke design also demands performance empathy.
When you visualize a data set, each slicer, card and
matrix is a query waiting to pounds on capacity. Layering
twenty filters on a single page may look clever, but
it will turn interactive exploration into molasses. Use bookmarks to
hide visual clutter, separate summary dashboards from deep explorations, paginate
(11:58):
detail views. The more predictable your query pattern, the fewer
support tickets you'll generate about powerbi being slow, which spoiler
alert usually means the report designer ignored basic logic. Now,
let's touch on consistency. Every spoke should follow shared UI standards,
color palettes, typography, layouts. It's not about esthetics, it's cognitive efficiency.
(12:19):
If finance users switch to a sales dashboard and instantly
know where to click, you've succeeded. Branded templates reduce friction
and support adoption. Establish a design system at the hub level,
approved fonds, regional color rules, margin constraints, then lock those
into the shared theme. Jason spokes should inherit style, not
improvise it like amateur painters. Navigation matters more than most
(12:40):
analysts admit. Users don't want detective work. They want direction.
Keep home pages clean, KPIs on top, filter's obvious context clear,
use tooltips and horver explanations to make every number self explanatory.
Every extra click is a tiny tax on comprehension. Great
user experience in powerbi is invisible. It feels obvious because
someone agonized labels that nobody notices. In a well planned
(13:02):
hub and spoke ecosystem, collaboration flows both ways. Analysts in
the spokes aren't rogue agents their scouts. When they find
a better calculated measure, they submit it back to the
hub for standardization. That's evolution through shared intelligence. The hub
then republishes the improved logic, instantly updating every department downstream.
This iterative loop turns experimentation into enterprise level progress. Without it,
(13:24):
every innovation dies in departmental isolation, like a lab experiment,
never peer reviewed. And here's the part people forget. Thin
reports are cheaper to maintain, They refresh faster, consume less capacity,
and scale effortlessly across audiences. One semantic model can support
dozens of tailored dashboards instead of sixty redundant models grinding servers.
You have a dozen nimble front ends referencing a single
(13:45):
trusted source. The payback isn't just performance, its governance with grace.
When you plan your spokes properly, the result is shockingly elegant.
Analysts move quickly, Executives trust the numbers, and it sleeps
through the night. Powerbi finally behaves like the enterprise whole.
It pretends to be structure the playground. Enforce light guard rails,
Keep reports thin, and you'll transform chaos into choreography. That's
(14:07):
the art of designing spokes that serve both speed and sanity.
Lean consistent and unapologetically efficient workspace structure and security models.
Let's talk about implementation, the part where strategy meets the
messy reality of permissions, folders, and humans. POWERBI is not
just about modeling data, It's about modeling responsibility. A workspace
is not a sandbox. It is a miniature sovereignty, and
(14:29):
if you don't design its borders deliberately, you'll discover too
late that every user thinks they're the king in a
proper hub and spoke deployment, workspace's map to business domains,
not to people or projects. You carve the structure by
department or function finance, hub, salespoke, operations, spoke, and so on.
Anything tied to individuals or temporary initiatives guarantees entropy. Workspaces
(14:49):
outlive people. Transient naming insures future confusion. Next, you define
workspace purpose. In each domain, create three clearly separated environments, development, test,
and production. Def workspaces are messy by design analysts, experiment,
prototype and break things. Test work spaces are clean mirrors
of PROD used to validate refreshes, row level security and
(15:11):
spelling errors in titles that somehow survive for approvals. Production
locked down tighter than an airlock. Only approved reports and
data sets reach it, and only designated deployers have publishing rights.
That separation is not bureaucracy. It's how you avoid having
deaf finals and appear on the cfo's dashboard. Now, let's
decode the workspace roles, because this is where innocence dies
POWERBI gives you four roles Viewer, contributor, member, and admin.
(15:34):
Assign them as if they were loaded weapons, because functionally
they are Viewers consume content, they can't share or edit.
They are the citizens. Contributors can publish and edit content,
but not manage permissions. They are your builders. Members can
assess and add users their subgovernors. Admins are absolute rulers
and should be counted on one hand per workspace. The
mistake companies make is giving everyone member or admin access
(15:58):
for convenience. It's not convenient. Its corruption over Privileging users
doesn't empower them, It erases accountability. Someone deletes a data
set and suddenly nobody knows who did it because everybody
could have create security groups in entra Idea that correspond
directly to these roles. One group for hub admins, one
for hub developers, and one for spoke viewers, etc. Never
add individuals manually. The moment you start assigning rights user
(16:19):
by user, you've guaranteed drift and confusion. Groups are your
armor against the chaos of turnover. When an employee leaves,
removing them from intra automatically strips every powerbi permission they had.
Manual removal equals guaranteed horror story later. Now, Layering security
isn't just about access, It's about contextual visibility. Row level
security ensures users only see the data that belongs to
(16:41):
their regional or functional scope. For instance, when a sales
rep opens a dashboard, they see only their territory's numbers,
not global totals. Object level security takes it further, hiding
whole tables or columns that shouldn't even exist in their reality,
like profit margins or confidential employee data. Implement these at
the hub so they propagate consistently across You define the
(17:01):
roles once and inheritance. Does the rest document these rules
explicitly somewhere visible ideally in your center of excellent SharePoint
page or within a powerbi app dedicated to governance list
Exactly which workspace follows which security model, which entragroup controls
it and which data sets are connected. Clarity prevents creative misinterpretation.
(17:22):
Then comes sensitivity classification. Every data set, every report, every
workspace gets a label public, internal, confidential, or restricted. This
label decides not just who can view it, but what
happens when it leaves Powerbi Microsoft three sixty five. Compliance
means that label travels export a table, email, a PDF,
embedded dashboard, and the label remains attached. Governance once again
(17:42):
becomes portable, like a passport that reminds users what country
their data belongs to. Now, for the physical structure inside
a workspace, create folders, data sets, reports, dashboards, PBX sources documentation.
They aren't folders in the literal sense, but subcategories through
naming conventions. Finn Moodel sales tells every R one it's
the sales data set inside finances hub. Consistent prefixes make
(18:04):
Powerbi workspaces readable at a glance. No one wants to
scroll through fifty artifacts named Report one through Report forty nine.
If the artifact naming requires a Rosetta stone, you've failed
your own design. Licensing ties into structure too. Every workspace
mapped to a HUBS should run on premium or fabric
capacity development workspaces can live on pro licenses, since prototype
refresh failures are training exercises, not incidents. When workloads scale,
(18:27):
you migrate to capacity based workspaces, So refreshes don't cannibalize
each other, and please forbid my workspace for anything other
than coffee fueled. Prototypes treat personal workspaces like posted notes, temporary, private,
and disposable. The moment real data enters my workspace, your
governance died. The ultimate purpose of this entire structure is traceability.
(18:48):
Every data set traceable to an owner, every report traceable
to a data set, every workspace tied to a group,
every group to a function. That's the ecosystem. You're replacing
chaos not with centralization, but with clarity, structure, distribution, federated ownership,
predictable security. Those are the underpinnings of a mature powerbi implementation.
Governance isn't a cage, it's scaffolding. Remove it and the
(19:09):
building collapses. When donewright workspaces don't multiply uncontrolled, they form
a predictable graph of domains and dependencies. Admins can glance
at usage metrics, trace lineage, and see instantly where refresh
bottlenecks lie with structured workspaces and discipline security implementation stops
being a euphemism for improvisations scaling with deployment pipelines and gateways.
(19:30):
Once the foundation is stable, scale becomes the next villain.
Early on, a few analysts can push PBX files around
manually and pretend that's sustainable. It isn't. As soon as
three departments share data sets, you'll need version control, promotion
stages and secure data ingress the grown up mechanics. Deployment
pipelines and gateways. Deployment pipelines are powerbi's answer to continuous
(19:52):
integration for data models you build once deploy thrice dev
test PROD. Each stage has its own workspace, but pipelines
manage promotion automatically. No more download PBX upload pbix. Instead,
you publish from dev run validation, then promote to test
with parameter swaps. That's where you confirm credentials, refresh schedules,
and row level security contexts behave. Only after approval does
(20:15):
the artifact march into broad identical in logic but contextually
configured for the live environment. Pipelines also handle version comparisons.
If someone fixes a measure in dev that breaks ten
visuals downstream. The pipeline shows the delta before promotion. You
can review diffs in deck scripts, them, Jason or even
model structure approvals turn subjective trust into verifiable process. Automating
(20:36):
these steps turns BI into software engineering. You move from
artisanal publishing to industrialized delivery. And no, this doesn't slow
you down. It prevents rollback panic at eight am on
executive reporting day. Next. Data gateways, These little unsung heroes
bridge your cloud service and on premises sources. Without them,
powerbi's refreshed jobs can't reach sequel servers sitting behind corporate firewalls.
(20:58):
Implement enterprise the data gateways in clusters two or more
nodes managed centrally. Gateways should never depend on one overburdened
desktop machine tugged under someone's desk. Use standardized service accounts,
not personal credentials, so authentication survives vacations and resignations. Monitor
gateways like you would server infrastructure. Powerbi offers metrics SPU
load latency, connection failures. A red gateway icon is not
(21:21):
an alert, It's an indictment that nobody was watching. Automate
notifications in power Automate or Azure monitor to catch failures
before managers notice. Stale dashboards now comes the clever orchestration
between deployment pipelines and gateways. You can assign different gateway
clusters per stage, a test gateway connecting to staging databases
and a production gateway pointing to hardened servers. Pipeline rules
(21:44):
handle these connection swaps automatically during promotion, keeping environments truly isolated.
One click moves a data set from dev onto prod
grade food without rewriting connection strings by hand. If your
architecture extends into fabric gateways, unify even more routing connecting
on prem data to lake houses and onwards to semantic
models still governed by these same principles of traceable connection
scaling also means automating refreshed scheduling and dependency sequencing. Instead
(22:08):
of human triggered chaos, you build refresh chains through pipeline
APIs or fabric data activator data set a refreshes it
success triggers data set b end result publishes notifications to teams.
This orchestration ensures reproducible performance even as model counts grow. Lastly,
include monitoring dashboards for governance activity track refrashderation, promoted pipeline
(22:28):
history and gateway uptime in a matter report the report
about your reports. That visibility keeps scaling honest. It turns
hidden complexity into measurable reliability. With deployment pipelines and hardened gateways,
your power bi ecosystem evolves from a loose federation of
dashboards into an automated data supply chain, auditible, recoverable, and scalable.
That's when you know planning has turned into architecture, and
(22:50):
architecture has turned into excellence. You can't buy your way
out of Powerbi chaos. You have to plan your way out.
The hub and spoke model isn't a configuration. It's a
contract between sanity and speed. The hub gives you the structure,
certified data sets, governed refreshes, defined ownership. The spokes give
you agility, rapid reports, quick iterations, business tailored insight. Together
(23:12):
they form an agreement, no duplication, no improvisational data drama.
Your next move is brutally simple. Map your existing sprawl,
list every workspace owner and data set. Identify which ones
deserve to become hub certified and which belong as spokes.
Create a deftest brought pipeline for at least one domain
finance or sales, and document every refresh and dependency that
(23:33):
one pilot becomes your working blueprint. Then establish visible governance,
naming conventions, documentation ownership dashboards so trust doesn't rely on
whispers but on structure. Teach analysts the joy of thin reporting, fast, reliable,
light weight. Celebrate every metric that gets standardized across teams.
That's a win worth more than a new visual type. Finally,
(23:53):
enforce habit loops. Monthly health reviews, lineage checks, and ownership
confirmation aren't rituals of control, their early warning systems
POWERBI, 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
interns spreadsheet is driving executive decisions. Congratulations, you've built a
(00:21):
decentralized empire of contradiction. Now let me clarify why you're here.
You're not learning how to use powerbi, 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.
Defining the power BI wild West, the problem of duplication.
Picture this. Every department in your company builds its own report.
(00:43):
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 an powerment. The
problem is that POWERBI makes it too easy to build fast.
(01:04):
The moment someone can connect an Excel file, they're suddenly
a data modeler. They save to one drive, 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
(01:24):
you stop trusting their numbers. Meetings devolve into crime scenes.
Everyone's examining conflicting evidence. The CFO swears the trend line
shows growth. The head of sales insists its decline. They're
both right because their data slices come from different refreshers, filters,
or strangely named tables like data final V three figx fixed.
That's the hidden cost of duplication. Every report becomes technically
correct within its own microcosm, but the organization loses a
(01:47):
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 have are the same.
Database performance tanks, gateways crash, and somewhere an IT engineer
silently resigns. This chaos doesn't happen because anyone's lazy. It
(02:09):
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
(02:30):
is the pattern of every power BIA 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, introducing hub and spoke architecture.
The 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
(02:52):
that make life bearable. The spokes are neighborhoods, creative, adaptive,
sometimes noisy, but connected by design. Without the hub, the
neighborhoods these into chaos. Without the spokes, the city stagnates.
In power bi terms, the hub holds your certified semantic models,
shared data sets, and standardized measures the official truth. The
spokes are your departmental workspaces. Sales, finance, HR build for exploration,
(03:16):
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 build a dashboard, it references the
certified financial data set. 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
(03:39):
a hub in spoke isn't glamorous. Its maintenance of intellectual hygiene.
You define data ownership by domain. Who maintains the sales model,
who validates the HR metrics. Each certified data set 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,
(04:01):
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 minutes before the board meeting. The genius of hubin
spoke is that it balances agility with reliability. Departments get
their self service, but it's anchored in enterprise trust. It
(04:23):
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
rareer than it should be. The Hub. Let's get serious
for a moment, because this is where most organizations fail spectacularly.
(04:45):
The Hub isn't a powerbi 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 data set to rule them all. A
shared data set is basically your organization's bloodstream. It carries clean,
(05:06):
standardized data from the source to every report that consumes it.
But unlike human blood, this data set 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
(05:30):
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 data set must have two parents,
(05:51):
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.
Refreshed schedules, DAX Performance Gateway reliability. Both names should be
right there in the data set description, because when that
refresh fails at two am or the CFO challenge is
a number at nine a M, you shouldn't need a
(06:12):
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 data set
deserves a read me, 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
(06:36):
definitions that nobody's updated since twenty twenty two. Then there's
certification POWERBI gives you two signals, promoted and certified. Promoted
means someone thinks this is good. Certified means the Data
Governance Board has checked it, blessed, 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,
(06:56):
not your homegrown version hiding in one drive. Certification also
comes with a cut ontability 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 data set connects visibly to its sources and all
downstream reports. When your CTO asks, if we deprecate that
(07:17):
sequel table, what breaks, you should have an instant answered,
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 POWERBI isn't GIT,
but you can treat it as code export PBIP files
store them in a repot tag releases. When analysts break something,
(07:38):
because they will, you can roll back to stability instead
of re engineering from memory. Governance without version control is
like driving without seat belts and insisting your reflexes are enough.
Capacity planning also lives at the hub level. Shared data
sets run on capacity. Capacity costs money. You don't put
test models or one of prototypes there. The hub is
production grade only optimized models, incremental refresh compressed columns the word.
(08:00):
Every refresh must be scheduled deliberately to avoid collision. Refreshing
fifteen models at eight am is not governance. It's CPU
arsen Now, let's address the political side. Governance means saying no, strategically, calmly,
and repeatedly. When a manager insists on adding a column
because they need it right now, the HUB team evaluates
it through impact, not emotion. How many reports depend on
(08:21):
this measure? Does it align with business definitions? Adding one
casual column might corrupt thirty downstream visuals? The Hub provides guardrails,
not customer service, but authority alone isn't enough. Visibility is
publish internal dashboards that track data set, health, refresh successes, failures,
refresh duration, data set size, number of connected reports. Let
(08:42):
leadership see governance in action. When executives visually witness uptime
at ninety nine percent, governance stops looking like red tape
and starts smelling like competence. Let's talk security. The Hub
enforces invisible discipline. That means row level security and object
level security are modeled here, not duct taped later by
the spokes. You define the filters one by region, division
or role, and every consuming report inherits them. No one copies,
(09:04):
ducks filters across ten workspaces like medieval scribes reproducing scripture.
Security is consistent inherited and auditible metadata. Hygiene rounds it out.
Sensitivity labels, and data loss prevention policies should originate in
the hub as defaults. Every certified data set carries its
classification like an ID badge, public, internal, confidential. When those
data sets flow into Excel or Outlook, the labels travel
(09:26):
with them. Governance isn't about blocking, It's about making trust portable. Finally, culture,
the hub is only as strong as the behavior it normalizes,
so institutionalized short show and tell sessions where departments present
improvements made to their reports or measures derived from Hub data.
Little rituals like that remind everyone that governance is collaboration,
not surveillance. The hub feeds the spokes, The spokes give
(09:49):
feedback to the hub. It's an ecological loop, not a monarchy.
When designed properly, the hub turns powerbi from a zoo
into a zoo with fences, feeding schedules, and a veterinarian.
The animals still roam, but nobody gets mauled. That is
shared governance done right. Predictable refreshes, defined ownership, certified semantics,
and a lineage so clear even auditors smile. That's the
(10:10):
infrastructure of trust you build before the chaos begins, and
once it exists, your spokes can finally innovate freely because
they know the hub has their back the spokes. Now
that the hub is keeping your data cleaned, certified, and
under control, it's time to talk about the parts everyone
actually sees the spokes. The spokes are where creativity lives,
where analysts experiment, and where business decisions happen at speed.
(10:33):
But freedom without structure is chaos. With better lighting, building
in the spoke means operating inside lanes that protect performance, consistency,
and user trust. A common temptation in the spokes is
to rebuild what's already in the hub. Duplicate measures, import
tables just in case, or tweak logic to match someone's
anecdotal truth. Don't. The purpose of the spoke is to
(10:54):
consume shared data, not reinterpret it. A thin report connects
life to certified data sets. It doesn't drag entire models
into memory. You're visualizing, not remodeling. Thinness is a virtue here,
fewer dependencies faster refreshes, lighter performance load. Think of each
spoke workspace as a showroom floor, elegantly displaying vehicles engineered
in the hub's factory. Optimization starts with model connections. Every
(11:16):
spoke should use live connections or direct links to semantic models,
not copies. That keeps data consistent and refreshed schedules centralized.
If someone insists on adding a localized measure, say a
region specific KPI, contain it within the report layer, documented
clearly as local logics so downstream users don't confuse it
with a certified field. Remember, traceability is oxygen. Without it,
(11:37):
creativity suffocates under ambiguity. Good spoke design also demands performance empathy.
When you visualize a data set, each slicer, card and
matrix is a query waiting to pounds on capacity. Layering
twenty filters on a single page may look clever, but
it will turn interactive exploration into molasses. Use bookmarks to
hide visual clutter, separate summary dashboards from deep explorations, paginate
(11:58):
detail views. The more predictable your query pattern, the fewer
support tickets you'll generate about powerbi being slow, which spoiler
alert usually means the report designer ignored basic logic. Now,
let's touch on consistency. Every spoke should follow shared UI standards,
color palettes, typography, layouts. It's not about esthetics, it's cognitive efficiency.
(12:19):
If finance users switch to a sales dashboard and instantly
know where to click, you've succeeded. Branded templates reduce friction
and support adoption. Establish a design system at the hub level,
approved fonds, regional color rules, margin constraints, then lock those
into the shared theme. Jason spokes should inherit style, not
improvise it like amateur painters. Navigation matters more than most
(12:40):
analysts admit. Users don't want detective work. They want direction.
Keep home pages clean, KPIs on top, filter's obvious context clear,
use tooltips and horver explanations to make every number self explanatory.
Every extra click is a tiny tax on comprehension. Great
user experience in powerbi is invisible. It feels obvious because
someone agonized labels that nobody notices. In a well planned
(13:02):
hub and spoke ecosystem, collaboration flows both ways. Analysts in
the spokes aren't rogue agents their scouts. When they find
a better calculated measure, they submit it back to the
hub for standardization. That's evolution through shared intelligence. The hub
then republishes the improved logic, instantly updating every department downstream.
This iterative loop turns experimentation into enterprise level progress. Without it,
(13:24):
every innovation dies in departmental isolation, like a lab experiment,
never peer reviewed. And here's the part people forget. Thin
reports are cheaper to maintain, They refresh faster, consume less capacity,
and scale effortlessly across audiences. One semantic model can support
dozens of tailored dashboards instead of sixty redundant models grinding servers.
You have a dozen nimble front ends referencing a single
(13:45):
trusted source. The payback isn't just performance, its governance with grace.
When you plan your spokes properly, the result is shockingly elegant.
Analysts move quickly, Executives trust the numbers, and it sleeps
through the night. Powerbi finally behaves like the enterprise whole.
It pretends to be structure the playground. Enforce light guard rails,
Keep reports thin, and you'll transform chaos into choreography. That's
(14:07):
the art of designing spokes that serve both speed and sanity.
Lean consistent and unapologetically efficient workspace structure and security models.
Let's talk about implementation, the part where strategy meets the
messy reality of permissions, folders, and humans. POWERBI is not
just about modeling data, It's about modeling responsibility. A workspace
is not a sandbox. It is a miniature sovereignty, and
(14:29):
if you don't design its borders deliberately, you'll discover too
late that every user thinks they're the king in a
proper hub and spoke deployment, workspace's map to business domains,
not to people or projects. You carve the structure by
department or function finance, hub, salespoke, operations, spoke, and so on.
Anything tied to individuals or temporary initiatives guarantees entropy. Workspaces
(14:49):
outlive people. Transient naming insures future confusion. Next, you define
workspace purpose. In each domain, create three clearly separated environments, development, test,
and production. Def workspaces are messy by design analysts, experiment,
prototype and break things. Test work spaces are clean mirrors
of PROD used to validate refreshes, row level security and
(15:11):
spelling errors in titles that somehow survive for approvals. Production
locked down tighter than an airlock. Only approved reports and
data sets reach it, and only designated deployers have publishing rights.
That separation is not bureaucracy. It's how you avoid having
deaf finals and appear on the cfo's dashboard. Now, let's
decode the workspace roles, because this is where innocence dies
POWERBI gives you four roles Viewer, contributor, member, and admin.
(15:34):
Assign them as if they were loaded weapons, because functionally
they are Viewers consume content, they can't share or edit.
They are the citizens. Contributors can publish and edit content,
but not manage permissions. They are your builders. Members can
assess and add users their subgovernors. Admins are absolute rulers
and should be counted on one hand per workspace. The
mistake companies make is giving everyone member or admin access
(15:58):
for convenience. It's not convenient. Its corruption over Privileging users
doesn't empower them, It erases accountability. Someone deletes a data
set and suddenly nobody knows who did it because everybody
could have create security groups in entra Idea that correspond
directly to these roles. One group for hub admins, one
for hub developers, and one for spoke viewers, etc. Never
add individuals manually. The moment you start assigning rights user
(16:19):
by user, you've guaranteed drift and confusion. Groups are your
armor against the chaos of turnover. When an employee leaves,
removing them from intra automatically strips every powerbi permission they had.
Manual removal equals guaranteed horror story later. Now, Layering security
isn't just about access, It's about contextual visibility. Row level
security ensures users only see the data that belongs to
(16:41):
their regional or functional scope. For instance, when a sales
rep opens a dashboard, they see only their territory's numbers,
not global totals. Object level security takes it further, hiding
whole tables or columns that shouldn't even exist in their reality,
like profit margins or confidential employee data. Implement these at
the hub so they propagate consistently across You define the
(17:01):
roles once and inheritance. Does the rest document these rules
explicitly somewhere visible ideally in your center of excellent SharePoint
page or within a powerbi app dedicated to governance list
Exactly which workspace follows which security model, which entragroup controls
it and which data sets are connected. Clarity prevents creative misinterpretation.
(17:22):
Then comes sensitivity classification. Every data set, every report, every
workspace gets a label public, internal, confidential, or restricted. This
label decides not just who can view it, but what
happens when it leaves Powerbi Microsoft three sixty five. Compliance
means that label travels export a table, email, a PDF,
embedded dashboard, and the label remains attached. Governance once again
(17:42):
becomes portable, like a passport that reminds users what country
their data belongs to. Now, for the physical structure inside
a workspace, create folders, data sets, reports, dashboards, PBX sources documentation.
They aren't folders in the literal sense, but subcategories through
naming conventions. Finn Moodel sales tells every R one it's
the sales data set inside finances hub. Consistent prefixes make
(18:04):
Powerbi workspaces readable at a glance. No one wants to
scroll through fifty artifacts named Report one through Report forty nine.
If the artifact naming requires a Rosetta stone, you've failed
your own design. Licensing ties into structure too. Every workspace
mapped to a HUBS should run on premium or fabric
capacity development workspaces can live on pro licenses, since prototype
refresh failures are training exercises, not incidents. When workloads scale,
(18:27):
you migrate to capacity based workspaces, So refreshes don't cannibalize
each other, and please forbid my workspace for anything other
than coffee fueled. Prototypes treat personal workspaces like posted notes, temporary, private,
and disposable. The moment real data enters my workspace, your
governance died. The ultimate purpose of this entire structure is traceability.
(18:48):
Every data set traceable to an owner, every report traceable
to a data set, every workspace tied to a group,
every group to a function. That's the ecosystem. You're replacing
chaos not with centralization, but with clarity, structure, distribution, federated ownership,
predictable security. Those are the underpinnings of a mature powerbi implementation.
Governance isn't a cage, it's scaffolding. Remove it and the
(19:09):
building collapses. When donewright workspaces don't multiply uncontrolled, they form
a predictable graph of domains and dependencies. Admins can glance
at usage metrics, trace lineage, and see instantly where refresh
bottlenecks lie with structured workspaces and discipline security implementation stops
being a euphemism for improvisations scaling with deployment pipelines and gateways.
(19:30):
Once the foundation is stable, scale becomes the next villain.
Early on, a few analysts can push PBX files around
manually and pretend that's sustainable. It isn't. As soon as
three departments share data sets, you'll need version control, promotion
stages and secure data ingress the grown up mechanics. Deployment
pipelines and gateways. Deployment pipelines are powerbi's answer to continuous
(19:52):
integration for data models you build once deploy thrice dev
test PROD. Each stage has its own workspace, but pipelines
manage promotion automatically. No more download PBX upload pbix. Instead,
you publish from dev run validation, then promote to test
with parameter swaps. That's where you confirm credentials, refresh schedules,
and row level security contexts behave. Only after approval does
(20:15):
the artifact march into broad identical in logic but contextually
configured for the live environment. Pipelines also handle version comparisons.
If someone fixes a measure in dev that breaks ten
visuals downstream. The pipeline shows the delta before promotion. You
can review diffs in deck scripts, them, Jason or even
model structure approvals turn subjective trust into verifiable process. Automating
(20:36):
these steps turns BI into software engineering. You move from
artisanal publishing to industrialized delivery. And no, this doesn't slow
you down. It prevents rollback panic at eight am on
executive reporting day. Next. Data gateways, These little unsung heroes
bridge your cloud service and on premises sources. Without them,
powerbi's refreshed jobs can't reach sequel servers sitting behind corporate firewalls.
(20:58):
Implement enterprise the data gateways in clusters two or more
nodes managed centrally. Gateways should never depend on one overburdened
desktop machine tugged under someone's desk. Use standardized service accounts,
not personal credentials, so authentication survives vacations and resignations. Monitor
gateways like you would server infrastructure. Powerbi offers metrics SPU
load latency, connection failures. A red gateway icon is not
(21:21):
an alert, It's an indictment that nobody was watching. Automate
notifications in power Automate or Azure monitor to catch failures
before managers notice. Stale dashboards now comes the clever orchestration
between deployment pipelines and gateways. You can assign different gateway
clusters per stage, a test gateway connecting to staging databases
and a production gateway pointing to hardened servers. Pipeline rules
(21:44):
handle these connection swaps automatically during promotion, keeping environments truly isolated.
One click moves a data set from dev onto prod
grade food without rewriting connection strings by hand. If your
architecture extends into fabric gateways, unify even more routing connecting
on prem data to lake houses and onwards to semantic
models still governed by these same principles of traceable connection
scaling also means automating refreshed scheduling and dependency sequencing. Instead
(22:08):
of human triggered chaos, you build refresh chains through pipeline
APIs or fabric data activator data set a refreshes it
success triggers data set b end result publishes notifications to teams.
This orchestration ensures reproducible performance even as model counts grow. Lastly,
include monitoring dashboards for governance activity track refrashderation, promoted pipeline
(22:28):
history and gateway uptime in a matter report the report
about your reports. That visibility keeps scaling honest. It turns
hidden complexity into measurable reliability. With deployment pipelines and hardened gateways,
your power bi ecosystem evolves from a loose federation of
dashboards into an automated data supply chain, auditible, recoverable, and scalable.
That's when you know planning has turned into architecture, and
(22:50):
architecture has turned into excellence. You can't buy your way
out of Powerbi chaos. You have to plan your way out.
The hub and spoke model isn't a configuration. It's a
contract between sanity and speed. The hub gives you the structure,
certified data sets, governed refreshes, defined ownership. The spokes give
you agility, rapid reports, quick iterations, business tailored insight. Together
(23:12):
they form an agreement, no duplication, no improvisational data drama.
Your next move is brutally simple. Map your existing sprawl,
list every workspace owner and data set. Identify which ones
deserve to become hub certified and which belong as spokes.
Create a deftest brought pipeline for at least one domain
finance or sales, and document every refresh and dependency that
(23:33):
one pilot becomes your working blueprint. Then establish visible governance,
naming conventions, documentation ownership dashboards so trust doesn't rely on
whispers but on structure. Teach analysts the joy of thin reporting, fast, reliable,
light weight. Celebrate every metric that gets standardized across teams.
That's a win worth more than a new visual type. Finally,
(23:53):
enforce habit loops. Monthly health reviews, lineage checks, and ownership
confirmation aren't rituals of control, their early warning systems
Popular Podcasts
Las Culturistas with Matt Rogers and Bowen Yang
Ding dong! Join your culture consultants, Matt Rogers and Bowen Yang, on an unforgettable journey into the beating heart of CULTURE. Alongside sizzling special guests, they GET INTO the hottest pop-culture moments of the day and the formative cultural experiences that turned them into Culturistas. Produced by the Big Money Players Network and iHeartRadio.
The Joe Rogan Experience
The official podcast of comedian Joe Rogan.
Stuff You Should Know
If you've ever wanted to know about champagne, satanism, the Stonewall Uprising, chaos theory, LSD, El Nino, true crime and Rosa Parks, then look no further. Josh and Chuck have you covered.