Guide sections

31 sections from the master guidelines, rendered with their tables, checklists and evidence callouts intact.

  1. 1PurposeThis handbook consolidates the Power BI UX/UI guidance developed across our earlier discussions, interactive guides, prototypes and migration work. It is intend
  2. 2Core Design Principles
  3. 3Power BI for UX Designers — Getting StartedPower BI is an analytical report platform, not a general-purpose responsive application framework. The most common design failure is to prototype a web applicat
  4. 4Power BI Architecture Relevant to UX
  5. 5Design System StrategyThe recovered enterprise direction is to reuse the existing company design system rather than create a second standalone Power BI design system. The Power BI-sp
  6. 6Foundations
  7. 7Complete Power BI Component & Capability InventoryThe recovered interactive guide contained 133 catalog entries. That catalog intentionally mixed native Power BI visuals/features with Nudge BI representations,
  8. 8Table & Matrix StandardThe reusable standard should be a configuration of native Table and Matrix, not a new custom table control.
  9. 9Filters & SlicersUse slicers for frequently changed, user-facing controls and the Filters pane for less frequent or more technical filtering. The user must be able to understand
  10. 10Interaction Patterns
  11. 11Navigation ArchitectureThe terminology recovered from the page-flow discussions is:
  12. 12Reusable Page PatternsThe later guide expanded the earlier six templates into 24 page archetypes. The archetype tells you what the page is for; the template tells you how that archet
  13. 13Page Composition Patternstext
  14. 14KPI & Scorecard PatternsA KPI should make the primary value, comparison basis and status legible without forcing the user to decode several competing numbers.
  15. 15Chart Selection Guide- Pie / donut: difficult precise angle/area comparison; keep to a few obvious categories.
  16. 16Dashboard / Report UX Heuristics
  17. 17AccessibilityAccessibility is part of each component specification and the Definition of Ready, not a final visual-polish task.
  18. 18Responsive Design & Screen SizesPower BI should not be designed as if it were a CSS-responsive website. Desktop report pages use a configured canvas and are scaled/fitted in the viewer. Phone
  19. 19Power BI Restrictions Designers Must Know
  20. 20Native vs Custom Decision FrameworkUse the lowest-complexity layer that satisfies the analytical requirement.
  21. 21Reusable System Above the Visual LayerThe central design-system concept recovered from multiple discussions is:
  22. 22Figma → Power BI Workflowtext
  23. 23Designer → Developer HandoffUse a compact per-page specification:
  24. 24Definition of Ready for Power BI Page DevelopmentA page is ready when the team can implement and test it without unresolved design or data assumptions.
  25. 25Migration Pattern: Existing Report → New Power BI PageThe migration work established that redesign should not start by tracing the old screen one-to-one. Work with business stakeholders to decide what from the lega
  26. 26Common Anti-Patterns
  27. 27Recommended Reusable LibraryThe library should be governed from foundations downward. A change to company tokens should flow through mappings; a new page pattern should not redefine brand
  28. 28Practical Examples
  29. 29Glossary
  30. 30Open Questions / Unresolved Areas
  31. 31Source / Decision HistoryThis section records the evolution that could be recovered from previous discussions and stored artifacts.