Page pattern

Monitoring

Answer whether performance is developing as expected, on a recurring rhythm, with a stable layout.

OrientationBasicArchetype: Monitoring / Operational
Typical user questions
  • Is performance developing as expected?
  • Did anything change since the last review?
  • Are we still within the norm?

Monitoring — 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
Current KPI vs target vs previous periodkpi
Actual€8.4M
Target€8.5M
Difference€-89kvs Budget€8.5M -101%Attention

Gap €-89k (-1%) against target.

Trend with reference linetrend
W1W2W3W4W5W6W7W8W9W10W11W12W13
Changes / alertsexceptions
Supporting breakdownbreakdown
Level: department

Bars: Revenue · vertical marker: Budget

What Power BI would do
  • Interact with a slicer, a bar or a navigation button to see the native behaviour described here.

Monitoring / Operational — archetype wireframe

[ Filters ] [ Status KPIs ] [ Exceptions / alerts ] [ Operational trend ] [ Worklist / detail ]

Simulation of native Power BI behaviour
Zone 1
Filters
Zone 2
Status KPIs
Zone 3
Exceptions / alerts
Zone 4
Operational trend
Zone 5
Worklist / detail

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

Designer

Components: Cards, Tables, Matrix, Conditional formatting, Charts, Slicers

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 detail**.

Navigation: Exception detail

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