Lessons learned: Governance and Adoption for Power BI
summary
Shows a practical Power BI governance roadmap with concrete failures and fixes: blueprinting often takes up to one year, dataset refreshes sometimes exceed refresh times > hours, and capacity requests routinely stall. Demonstrates building a Center of Excellence (centralized, unified, federated, or decentralized), finds missing roles (no Power Admin, three product owners causing priority conflicts), uses Tabular Editor for best practice reviews, runs office hours and mentoring, and reports that disabling export to Excel provokes major pushback.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 3:21Power BI adoption starts organically
- 6:25Governance blueprint
- 8:44Governance theory
- 10:56Sponsorship role
- 12:20Power BI challenges case
- 14:07Content scope and ownership
- 16:52BI content ownership strategies
- 19:08Roles and responsibilities
- 20:31BI team pitfalls case
- 22:36Power BI Center of Excellence
- 25:30CoE: centralized vs federated
- 27:17Responsibilities of a Center of Excellence
- 29:47Governance via standards
- 31:13Capacity and cost monitoring
- 33:37User enablement strategies
- 36:24Training and learning paths
- 37:50Office hours and mentoring
- 40:30Community of practice
- 42:14Support structures
- 44:24Change management
- 45:48Governance roadmap
- 47:56Q&A
related talks
50mThe Path to Success with Power BI: Best Practices
50mBuilding an Empire - Implementing Power BI Step by Step
51mThe accidental administrator's guide Power BI
48mCombine Power BI with External Tools
01h 21mA Deep Dive into User-Centered Power BI Report Design
58mReal world PowerBI
22m5 Things You Can Do to build better looking reports
50mTroubleshooting Power BI Reports