Playground
  • Introduction
  • Components

Needs-based view

Views shaped by the user’s immediate purpose rather than fixed interface conventions. The same underlying data presents itself differently depending on whether the user needs to monitor, analyse, or investigate—configuring granularity, metrics, and navigation mechanisms to match the task at hand.

Within the view system, needs-based views demonstrate how framing determines representation.

Variants

Monitoring and situational awareness

Maintain operational awareness without deep investigation. Emphasises aggregate metrics, trends, and status indicators in high-level overview format. Users track state changes and identify anomalies requiring attention.

Typical configuration: Zoomed-out collection view with summary-level items, auto-refresh, visual indicators for status changes.

Analytical exploration

Draw conclusions through structured investigation. Provides medium granularity with comparison tools, filtering, and grouping capabilities. Users explore patterns, test hypotheses, generate insights.

Typical configuration: Collection view with flexible filtering/sorting, multiple representation options (table, cards, charts), attribute selection.

Drilldown investigation

Investigate specific entities by progressively narrowing focus. Users navigate from collection overview through filtering to individual item detail.

Typical configuration: Linked views enabling collection → item transitions, preserved filter state, breadcrumb navigation for context.

Resources & references

  • PatternFly Dashboard
  • Carbon Dashboards

Related patterns

Related

  • Data view — Collection representations with framing intents
  • Item view — Single-entity representations at different granularities
  • Charting data — the monitoring variant is largely composed of charts; the needs-based framing decides which comparisons each chart must support