Have you ever heard the term “Excel hell”?
Odds are, if you’re reading this blog you’ve heard it, and possibly lived it once or twice. If not, you may want to take a minute to search online and discover what the internet has to say about it.
Managed self-service BI with Power BI is one way to escape or avoid Excel hell, but any self-service data tool brings with it some of the same risks that Excel brings. Power BI introduces guardrails to make it easier to manage the work that self-service authors produce, but wouldn’t it be nice to address the problem at its root, and prevent unwanted content from being shared in the first place?
The video introduces a set of techniques to gain explicit stakeholder buy-in. For the enterprise Power BI customers I work with, these steps are usually prerequisites to getting a Pro license and permission to publish to the Power BI service, but they may be required for other activities as well.
- Ask for it – rather than automatically issuing licenses in bulk, issue licenses only to users who explicitly request them
- Take a test – require users to take and pass a simple test
- Complete training – require users to attend Dashboard in a Day or similar introductory training
None of these barriers is designed to keep anyone from getting access to the tools and data they need. They’re designed to make people work for it.
As mentioned in earlier posts and videos, humans are complicated and tricky, but most people value what they earn more than they value what they’re given. And if someone works to earn the ability to publish and share data and reports, they’re more likely to think twice before they publish something and forget it.
This is a small but effective step that can reduce the ongoing effort required to manage and govern the content published to the Power BI service. And if you put the entry point to requesting access in your central portal, you’ll be helping reinforce the behaviors that will make your data culture grow, right from the beginning.
 Emphasis here on “simple” – every company I talked to who used this approach designed the test so that anyone could pass it.
 Power App, Customer Voice form, ServiceNow ticket, whatever fits your processes and requirements.