Level: Beginner / Non-Technical
Target Audience: Business Analysts / Project Managers / Data Analytics Project Stakeholders or people who have an interest in this area.
Traditional Reporting vs Power BI
| Traditional Reporting | Power BI |
| Static | Interactive |
| Fixed layout | Self-service exploration |
| Print-oriented | Insight-oriented |
| One report per question | One report answers many questions |
| User consumes | User investigates |
| Large tabular reports | Visual storytelling |
Demonstrate “Bad Requests”
Typical bad requests:
- “Can you recreate this Excel workbook exactly?”
- “Can you make all 400 columns visible?”
- “Can you fit everything on one page?”
- “Can we export everything to Excel?”
- “Can we have 25 pie charts?”
- “Can we have a tab for every department?”
Good Power BI Requests
Great Power BI requests focus on:
- decisions
- actions
- trends
- exceptions
- root causes
- interactivity
Power BI Strengths
- drill-down
- drill-through
- bookmarks
- tooltips
- decomposition trees
- AI visuals
- natural language Q&A
- mobile layouts
- semantic models
- self-service analytics
As demonstrated in the following link … Power BI Best Practice Recommendation
Closing
- The goal of Power BI is not to recreate old reporting systems
- The goal is to help people make better decisions faster.
- The most successful Power BI projects happen when business users understand the art of the possible.
- Great analytics starts with asking better questions.