Mastering Power BI Design with User-Centric Frameworks
summary
A consulting engagement runs user research with field workers and leadership, tests multiple dashboards, and finds adoption fails because reports are slow, cluttered, lagged and irrelevant rather than because of low data literacy; leadership and field users perform equally on interpretation. Outcomes: preference for light mode, high‑contrast colors with explanatory text and minimal interactivity; recommend building KPI trees and driver maps, style guides and iterative team involvement from project start, and only using custom visuals for density or performance needs.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 1:35Challenges in report adoption
- 3:34Developer roles and experience
- 6:15Waterfall project limitations
- 8:56UX outputs and design pain
- 11:56Navigation and wireframing
- 14:45Refining the design process
- 17:45Human centered design origins
- 21:42Conducting user research
- 24:26Testing audience assumptions
- 26:43Design preferences and usage
- 31:29Functionality vs simplicity
- 38:58Using KPI trees for design
- 44:26Iterative report evolution
related talks
01h 21mA Deep Dive into User-Centered Power BI Report Design
27mVisual Design - Do not let Data be your cul-de-sac!
37mMaking Informed Decisions: Guidelines for Creating an Effective Dashboard
22m5 Things You Can Do to build better looking reports
53mDashboards: interactive data visualization
01h 04mBest Practice Mobile Dashboard Design
01h 10mStorytelling through data
16mDesigning for Accessibility