Reusable Page Patterns

The 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 archetype is composed.

Landing / Navigation

• Goal: Enter a report, domain or report section and choose where to go next.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Header / context, Navigation cards / links, Shortcuts / help
• Recommended visuals/components: Buttons, Page navigator, Text boxes, Images
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Overview or report section.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Overview or report section
• Native Power BI 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.
• Wireframe structure:

[ Header / context ]
[ Navigation cards / links ]
[ Shortcuts / help ]

Overview / Summary

• Goal: Understand overall status and the most important changes or exceptions at a glance.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Header + filters, KPI summary, Primary trend / status, Breakdown / exceptions, Detail on demand
• Recommended visuals/components: Cards, Slicers, Line/Column charts, Bar charts, Matrix
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Analysis or drillthrough.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Analysis or drillthrough
• Native Power BI 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.
• Wireframe structure:

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

KPI / Scorecard

• Goal: Monitor targets, benchmarks and KPI health across a set of measures.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Context + filters, KPI cards, Target comparison, KPI trends, Breakdown
• Recommended visuals/components: Cards, KPI visual, Bar/Column charts, Matrix, Sparklines
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: KPI analysis or detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: KPI analysis or detail
• Native Power BI 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.
• Wireframe structure:

[ Context + filters ]
[ KPI cards ]
[ Target comparison ]
[ KPI trends ]
[ Breakdown ]

Monitoring / Operational

• Goal: See what needs attention now and support recurring operational review.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Filters, Status KPIs, Exceptions / alerts, Operational trend, Worklist / detail
• Recommended visuals/components: Cards, Tables, Matrix, Conditional formatting, Charts, Slicers
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Exception detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Exception detail
• Native Power BI 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.
• Wireframe structure:

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

Analysis / Explore

• Goal: Investigate a business question by changing dimensions, filters or analytical views.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Filters / controls, Primary analysis, Comparison / breakdown, Supporting analysis, Detail
• Recommended visuals/components: Slicers, Field parameters, Charts, Matrix, Decomposition tree
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Focused analysis or detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Focused analysis or detail
• Native Power BI 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.
• Wireframe structure:

[ Filters / controls ]
[ Primary analysis ]
[ Comparison / breakdown ]
[ Supporting analysis ]
[ Detail ]

Trend / Development

• Goal: Understand how a measure changes over time and whether the direction is expected.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Context KPIs, Time controls, Main trend, Benchmark / comparison, Breakdown
• Recommended visuals/components: Line chart, Column chart, Cards, Slicers
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Comparison or detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Comparison or detail
• Native Power BI 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.
• Wireframe structure:

[ Context KPIs ]
[ Time controls ]
[ Main trend ]
[ Benchmark / comparison ]
[ Breakdown ]

Comparison

• Goal: Compare entities, periods, channels, categories or peers on a consistent basis.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Filters, Comparison KPIs, Primary comparison, Difference / variance, Detail table
• Recommended visuals/components: Bar/Column charts, Cards, Matrix, Small multiples where suitable
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Variance or entity detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Variance or entity detail
• Native Power BI 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.
• Wireframe structure:

[ Filters ]
[ Comparison KPIs ]
[ Primary comparison ]
[ Difference / variance ]
[ Detail table ]

Variance / Actual vs Target

• Goal: Show how actual performance differs from budget, target, norm or previous period.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Variance KPIs, Actual vs target, Variance visual, Contributors, Detail
• Recommended visuals/components: Cards, Waterfall, Bar/Column charts, Matrix
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Root-cause analysis.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Root-cause analysis
• Native Power BI 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.
• Wireframe structure:

[ Variance KPIs ]
[ Actual vs target ]
[ Variance visual ]
[ Contributors ]
[ Detail ]

Driver / Root-Cause Analysis

• Goal: Explain why a KPI, variance or outcome changed and identify the strongest contributors.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Problem / KPI, Key drivers, Contribution analysis, Supporting evidence, Detail
• Recommended visuals/components: Decomposition tree, Waterfall, Bar charts, Matrix
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Contributor drillthrough.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Contributor drillthrough
• Native Power BI 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.
• Wireframe structure:

[ Problem / KPI ]
[ Key drivers ]
[ Contribution analysis ]
[ Supporting evidence ]
[ Detail ]

Contribution / Breakdown

• Goal: Understand which categories or segments make up a total and which contribute most.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Total KPI, Category breakdown, Ranked contributors, Secondary context, Detail
• Recommended visuals/components: Bar charts, Stacked charts, Treemap, Matrix, Cards
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Category detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Category detail
• Native Power BI 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.
• Wireframe structure:

[ Total KPI ]
[ Category breakdown ]
[ Ranked contributors ]
[ Secondary context ]
[ Detail ]

Distribution

• Goal: Understand spread, concentration, variability and outliers rather than only averages.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Summary statistics, Distribution visual, Segments, Outliers, Detail records
• Recommended visuals/components: Scatter chart, Binned Column chart, Table; approved custom visual if required
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Outlier detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Outlier detail
• Native Power BI 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.
• Wireframe structure:

[ Summary statistics ]
[ Distribution visual ]
[ Segments ]
[ Outliers ]
[ Detail records ]

Segmentation

• Goal: Compare meaningful groups and identify differences in performance or behaviour.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Filters, Segment KPIs, Segment visual, Comparison, Detail
• Recommended visuals/components: Bar charts, Scatter chart, Matrix, Slicers
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Segment detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Segment detail
• Native Power BI 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.
• Wireframe structure:

[ Filters ]
[ Segment KPIs ]
[ Segment visual ]
[ Comparison ]
[ Detail ]

Search / Lookup

• Goal: Find a specific entity, item, store, article, partner or record using known attributes.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Search / filter area, Result count / context, Results table, Selection / actions
• Recommended visuals/components: Slicers, Text/search slicer patterns, Table, Matrix, Buttons
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Entity detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Entity detail
• Native Power BI 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.
• Wireframe structure:

[ Search / filter area ]
[ Result count / context ]
[ Results table ]
[ Selection / actions ]

List / Results

• Goal: Browse, filter, sort and compare a larger result set before opening one item.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Filters, Summary / count, Sortable results, Selection state, Detail action
• Recommended visuals/components: Table, Matrix, Slicers, Conditional formatting
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Entity detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Entity detail
• Native Power BI 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.
• Wireframe structure:

[ Filters ]
[ Summary / count ]
[ Sortable results ]
[ Selection state ]
[ Detail action ]

Entity Detail

• Goal: Understand one selected business entity in context.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Entity header, Summary KPIs, Trend, Attributes / breakdown, Related records
• Recommended visuals/components: Cards, Charts, Table, Matrix, Drillthrough
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Transaction or related detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Transaction or related detail
• Native Power BI 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.
• Wireframe structure:

[ Entity header ]
[ Summary KPIs ]
[ Trend ]
[ Attributes / breakdown ]
[ Related records ]

Transaction Detail

• Goal: Inspect exact underlying records, events or transactions supporting an analysis.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Context, Summary, Transaction table, Supporting metrics
• Recommended visuals/components: Table, Matrix, Cards, Slicers
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Back to analysis.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Back to analysis
• Native Power BI 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.
• Wireframe structure:

[ Context ]
[ Summary ]
[ Transaction table ]
[ Supporting metrics ]

Exception / Attention

• Goal: Prioritize abnormalities, risks or underperformance that require investigation or action.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Exception KPIs, Prioritized list, Severity / reason, Trend / evidence, Detail
• Recommended visuals/components: Cards, Conditional formatting, Table/Matrix, Bar charts
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Exception drillthrough.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Exception drillthrough
• Native Power BI 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.
• Wireframe structure:

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

Forecast / Planning

• Goal: Understand the expected future state and compare it with targets or capacity.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Current state, Forecast KPIs, Trend + forecast, Assumptions / drivers, Breakdown
• Recommended visuals/components: Line chart, Cards, Slicers, Analytics features where supported
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Scenario or plan detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Scenario or plan detail
• Native Power BI 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.
• Wireframe structure:

[ Current state ]
[ Forecast KPIs ]
[ Trend + forecast ]
[ Assumptions / drivers ]
[ Breakdown ]

Scenario / What-if

• Goal: Evaluate how changing one or more assumptions affects an outcome.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Baseline, Parameters, Scenario output, Delta / impact, Breakdown
• Recommended visuals/components: What-if parameters, Slicers, Cards, Charts
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Decision / monitoring.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Decision / monitoring
• Native Power BI 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.
• Wireframe structure:

[ Baseline ]
[ Parameters ]
[ Scenario output ]
[ Delta / impact ]
[ Breakdown ]

Geographic / Location

• Goal: Understand spatial differences and compare performance across locations or regions.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: KPIs / filters, Map, Ranking / comparison, Location breakdown, Detail
• Recommended visuals/components: Azure Maps, Cards, Bar charts, Table/Matrix
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Location detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Location detail
• Native Power BI 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.
• Wireframe structure:

[ KPIs / filters ]
[ Map ]
[ Ranking / comparison ]
[ Location breakdown ]
[ Detail ]

Process / Funnel

• Goal: Understand progression through stages, conversion and bottlenecks.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Volume KPIs, Stage progression, Conversion / loss, Bottlenecks, Detail
• Recommended visuals/components: Funnel, Bar/Column charts, Cards, Matrix
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Stage detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Stage detail
• Native Power BI 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.
• Wireframe structure:

[ Volume KPIs ]
[ Stage progression ]
[ Conversion / loss ]
[ Bottlenecks ]
[ Detail ]

Reconciliation / Audit

• Goal: Validate numbers, expose mismatches and support traceability between sources or calculations.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Status summary, Difference KPIs, Mismatch table, Source / record detail
• Recommended visuals/components: Cards, Table, Matrix, Conditional formatting
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Record detail.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Record detail
• Native Power BI 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.
• Wireframe structure:

[ Status summary ]
[ Difference KPIs ]
[ Mismatch table ]
[ Source / record detail ]

Narrative / Explanation

• Goal: Explain a result or decision using a deliberate sequence of key messages and evidence.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Key message, Evidence, Supporting charts, Explanation, Next action
• Recommended visuals/components: Text boxes, Cards, Charts, Smart narrative where appropriate
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Supporting analysis.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Supporting analysis
• Native Power BI 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.
• Wireframe structure:

[ Key message ]
[ Evidence ]
[ Supporting charts ]
[ Explanation ]
[ Next action ]

Help / Definitions

• Goal: Explain report usage, metric definitions, ownership, scope and analytical conventions.
• Primary user question: Derived from the page purpose; write it explicitly before implementation.
• Recommended sections: Intro / purpose, Navigation help, Definitions, Metric glossary, Ownership / links
• Recommended visuals/components: Text boxes, Buttons, Shapes, Page navigator
• Interaction model: Use only interactions that support the page's next analytical step; typical next level: Return to report.
• Information hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.
• Suitable navigation: Return to report
• Native Power BI 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.
• Wireframe structure:

[ Intro / purpose ]
[ Navigation help ]
[ Definitions ]
[ Metric glossary ]
[ Ownership / links ]

Six core reusable templates recovered from the guide