Design Principle
Analytics interfaces should move from anomalies and questions toward causes, not just show chart collections.
Principle
Analytics interfaces should move from anomalies and questions toward causes, not just show chart collections.
Design action
The overview shows trends, anomalies, and key segments; click-through reveals dimension breakdown, raw records, and next actions.
Examples
Positive example: Product analytics, operations monitoring, sales reports, support quality, and finance dashboards. Counterexample: All charts are tiled with no question-led path.
Apply when
Product analytics, operations monitoring, sales reports, support quality, and finance dashboards. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/
Agent Directive
The overview shows trends, anomalies, and key segments; click-through reveals dimension breakdown, raw records, and next actions.