Page pattern

Exceptions / Attention

Reduce a large population to the few items that break a rule, ranked so work can start immediately.

OrientationIntermediateArchetype: Exception / Attention
Typical user questions
  • What requires my attention?
  • Which items are worst?
  • What changed since yesterday?

Exceptions / Attention — 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
Exception 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
Severity / category filtersfilters
DepartmentAll
Ranked exception listexceptions
Selected exception analysisdriver
W1W2W3W4W5W6W7W8W9W10W11W12W13
Action / drillthroughnavigation
What Power BI would do
  • Interact with a slicer, a bar or a navigation button to see the native behaviour described here.

Exception / Attention — archetype wireframe

[ Exception KPIs ] [ Prioritized list ] [ Severity / reason ] [ Trend / evidence ] [ Detail ]

Simulation of native Power BI behaviour
Zone 1
Exception KPIs
Zone 2
Prioritized list
Zone 3
Severity / reason
Zone 4
Trend / evidence
Zone 5
Detail

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

Designer

Components: Cards, Conditional formatting, Table/Matrix, Bar charts

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: **Exception drillthrough**.

Navigation: Exception 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