Page pattern

Distribution / Segmentation

Show how a population is spread and which segments carry the volume or the risk.

AnalysisIntermediateArchetype: Distribution
Typical user questions
  • How is this spread across items?
  • Which segment carries most of the value?
  • Are there outliers?

Distribution / Segmentation — 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
Population 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
Distributionbreakdown
Fresh: €2.4MBeverages: €1.7MGrocery: €1.7MNon-food: €1.4MHousehold: €1.2M
Ranked segmentscomparison
Level: department

Bars: Revenue · vertical marker: Budget

Segment tabledetail
5 rows
vs Budget
Fresh€2.4M€2.5M€608k -0.9%
Beverages€1.7M€1.7M€426k -0.7%
Grocery€1.7M€1.7M€426k -0.8%
Non-food€1.4M€1.4M€346k -1.4%
Household€1.2M€1.2M€291k -1.7%
Total€8.4M€8.5M€2.1M-1.0%
What Power BI would do
  • Interact with a slicer, a bar or a navigation button to see the native behaviour described here.

Distribution — archetype wireframe

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

Simulation of native Power BI behaviour
Zone 1
Summary statistics
Zone 2
Distribution visual
Zone 3
Segments
Zone 4
Outliers
Zone 5
Detail records

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

Designer

Components: Scatter chart, Binned Column chart, Table; approved custom visual if required

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

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