The Internal Power BI Lifecycle
Stage 1: Someone Knows Enough To Be ‘Dangerous’
It starts off well, like most things tend to do (what do they say about good intentions and paths…)
A motivated staff member, looking to solve a real problem within the business builds a few reports, connects some spreadsheets, publishes to the Power BI Services and suddenly the business gets a taste of real reporting.
But they don’t understand:
- Data Gateways
- Scheduled refresh infrastructure
- Version control
- Dataset design
- Row-level security
- API limits
- Governance
- Capacity planning
- Semantic modelling
- Change management
What has happened here though is that they’ve built a few reports but not an actual reporting system.
Stage 2: Things Break, So They Hire an IT Guy
- Refresh failures.
- Credential issues.
- Gateway offline.
- Reports not updating.
- Files too large.
- Everything slowing down.
So of course the business does the logical thing and phones the IT department or their Managed Services Provider. Except these people (as helpful as they are) aren’t BI engineers. They fix the gateway, patch some connectors, maybe restart the server - but they don’t rebuild the architecture, with the real challenge being that the underlying problems remain.
Stage 3: People Start Making Their Own Reports
Someone asks for a new metric, or a slightly different metric or another team wants a copy of an existing report this time they want it ‘customised.’
Since there is no semantic model and no data governance:
- People download datasets
- Modify reports
- Republish under their own workspace
- Create their own data sources
- Duplicate metrics
- Duplicate calculations
- Create different definitions of the same thing
When this happens it has multiple flow on effects as utilisation exists in six versions, gross profit is calculated four different ways and the WIP depends on which report you look at. When this happens, the real problem emerges which is that nobody trusts the numbers anymore
Stage 4: Weeks Pass and Everything Is a Mess
People leave and new people arrive and priorities change. Fast forward a few weeks and months and the organisation now has:
- Hundreds of abandoned datasets
- Dozens of unmanaged gateways
- Expired credentials
- Reports you cannot refresh
- Reports pointing to legacy exports no one maintains
- A Frankenstein folder of PBIX files
- No documentation
- No governance
- No central ownership
- And a shocking number of unused Power BI Pro licences
When we audit environments, it’s common to see 20–50 paid licences for people who haven’t logged in once. Does this sound familiar?
This is the point where most businesses finally call us.