Page pattern

Overview / Dashboard

Orient the user: overall status, the most important movement, and a clear route into deeper analysis. It answers “how are we doing” — not “why”.

OrientationBasicArchetype: Overview / Summary
Typical user questions
  • How are we performing right now?
  • Is anything clearly off track?
  • Where should I look next?

Overview / Dashboard — clickable example

Shared retail dataset. Every control works; the log shows what Power BI would change.

Simulation of native Power BI behaviour
Filter contextDepartment:All
Global filtersfilters
DepartmentAll
KPI summarykpi
Revenue€8.4Mvs Budget€8.5M -1%Attention
vs Previous year€8.4Mvs Previous year€8.3M +1.4%On track
Margin€2.1Mvs Benchmark€2.1M -0.2%Attention
Main trendtrend
W1W2W3W4W5W6W7W8W9W10W11W12W13
Target / benchmarkcomparison
€8.4Mtarget €8.5M
Performance breakdownbreakdown
Level: department

Bars: Revenue · vertical marker: Budget

Exceptions / attentionexceptions
Navigation to deeper analysisnavigation
What Power BI would do
  • Interact with a slicer, a bar or a navigation button to see the native behaviour described here.

Overview / Summary — archetype wireframe

[ Header + filters ] [ KPI summary ] [ Primary trend / status ] [ Breakdown / exceptions ] [ Detail on demand ]

Simulation of native Power BI behaviour
Zone 1
Header + filters
Zone 2
KPI summary
Zone 3
Primary trend / status
Zone 4
Breakdown / exceptions
Zone 5
Detail on demand

Reading order follows the zones above, top-left to bottom-right.

Designer

Components: Cards, Slicers, Line/Column charts, Bar charts, Matrix

Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.

Developer

Interaction: Use only interactions that support the page's next analytical step; typical next level: **Analysis or drillthrough**.

Navigation: Analysis or drillthrough

Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.

Common mistakes
Treating the archetype as a rigid screen; adding unrelated analytical tasks; duplicating controls already handled globally.
Related entries