Page pattern
Performance Analysis
Explain a performance level: how it developed, which drivers contributed, and where in the hierarchy the movement sits.
- “Why is this KPI above or below budget?”
- “Which departments drive the result?”
- “Is this a one-week effect or a trend?”
Performance Analysis — clickable example
Shared retail dataset. Every control works; the log shows what Power BI would change.
Gap €-89k (-1%) against target.
Bars: Revenue · vertical marker: Budget
| Rows | Revenue | Budget | vs Budget |
|---|---|---|---|
| €2.4M | €2.5M | -0.9% | |
| €1.7M | €1.7M | -0.7% | |
| €1.7M | €1.7M | -0.8% | |
| €1.4M | €1.4M | -1.4% | |
| €1.2M | €1.2M | -1.7% | |
| Total | €8.4M | €8.5M | -1.0% |
- Interact with a slicer, a bar or a navigation button to see the native behaviour described here.
Analysis / Explore — archetype wireframe
[ Filters / controls ] [ Primary analysis ] [ Comparison / breakdown ] [ Supporting analysis ] [ Detail ]
Reading order follows the zones above, top-left to bottom-right.
Components: Slicers, Field parameters, Charts, Matrix, Decomposition tree
Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
Interaction: Use only interactions that support the page's next analytical step; typical next level: **Focused analysis or detail**.
Navigation: Focused analysis or detail
Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.