The Gym Membership Fallacy: Why Self-Service BI Adoption Fails (and How to Fix It)

Buying a gym membership doesn't make you fit.
Giving someone a Power BI licence doesn't make an organisation data-driven.
Yet many self-service BI strategies follow exactly that logic: provide access, send a welcome email, run two days of training, and wait for adoption.
What follows is predictable.
Some users never start. Others build ten versions of the same metric. The most capable people become unofficial support desks. Governance reacts by adding restrictions — and “self-service” quietly becomes “please raise a ticket”.
The problem is not user motivation.
We designed technical access but failed to design a path to autonomy.
In this session, we'll use behavioural psychology and practical Power BI/Fabric patterns to explore four common adoption frictions: cognitive overload, fear of making mistakes, learned dependency and unclear ownership.
You will learn how to design progressive autonomy:
Access → Guidance → Guardrails → Ownership
We'll examine starter models, curated metrics, office hours, reusable patterns and CoE support as behavioural architecture — not just governance assets.
Because buying the membership was never the transformation.
Using the gym is.

3 AHA MOMENTS
Users duplicate reports because of the Endowment effect
Access without guidance creates learned helplessness, not empowerment
Over-choice paralyzes users — fewer options drive more usage
ROI
Higher self-service adoption without increasing support headcount
Faster time-to-insight as users follow the “guided path” by default
Measurable reduction in duplicated reports and shadow BI

Stop Babysitting, Start Delivering: DataOps for Fabric & Power BI Grown-Ups

Many BI teams spend more time babysitting pipelines than building value. Manual refreshes, brittle datasets, ad-hoc fixes, and undocumented workarounds—this isn’t analytics. And if your BI success depends on a hero developer fixing things at 11 p.m., you don’t have a platform—you have a survival strategy.
Microsoft Fabric promises an integrated, end-to-end analytics environment, but without DataOps it can quickly turn into just another playground for chaos: uncontrolled growth, firefighting, and silent errors. Meanwhile, BI teams don’t fail because they do too little - they fail because they do too much of the wrong work: rework, manual checks, duplicated logic, mismatched definitions, and dashboards that never reach “done”.
In this session, you’ll learn how Lean, Agile, and DevOps principles make DataOps flip this pattern—and how they translate directly into Fabric and Power BI. We’ll walk through practical ways to eliminate heroism and embed automation, quality, observability, and reproducibility into every step of the analytics lifecycle. The result is a calm, no-drama Fabric environment where reliability is the default.

Ask, Don't Build: The Coaching Questions That Save Your Power BI Project

Most analytics projects don't fail in Power BI Desktop.
They fail three weeks earlier, in a meeting where someone says: “We just need a simple sales dashboard.”
Everyone nods.
The data team starts modelling.
Three sprints later, the fact table is being rebuilt because the real problem was never a dashboard. A commercial leader needed to decide which customers required intervention before the end of the month.
This workshop is about the conversation before the architecture.
Using questioning patterns inspired by professional coaching, participants will practise how to slow down the rush to solution without turning requirements gathering into a three-hour interrogation.
We will work with realistic analytics requests and practise how to:
- distinguish a requested artefact from the decision it is supposed to support,
- contract for what “success” means before discussing visuals,
- surface assumptions without accusing the stakeholder of being wrong,
- explore multiple perspectives when business and engineering use the same word differently,
- translate the resulting clarity into model grain, metrics, and semantic design.
This is about learning to ask questions that create shared understanding before technical decisions become expensive.