The actor returns to the same underlying data with different purposes at different moments: a passing glance between tasks, a scheduled review, a deep dive into one concern. The data is already well presented — nothing is hidden — yet the recurring questions still take work to answer, and each moment brings a different amount of attention to spend on them.

This is what the word dashboard usually means. It names three separable things: an artefact (tiled charts on one screen), a use (monitoring at a glance), and an authorship (composed at design-time, fixed for everyone). This page holds the use — the purpose, whatever the look. The authorship stance is malleability’s. The artefact belongs to charting data.

Forces

• Generality vs. relevance — one general view can show everything, organised and visualised well, but deciding which of everything matters right now is left to the actor, and that inference is itself expert work.
• Density vs. attention — a view dense enough for the deep dive is too dense for the passing glance; one view cannot be honest to attention budgets that differ by orders of magnitude.
• Fit vs. upkeep — a hand-built view per question fits perfectly on day one and drifts from then on; the pre-built report is an expensive intermediary that lags behind the questions asked of it.

Solution

Shape what the view shows around the purpose — which data, at what level of detail, demanding how much attention — rather than presenting the data one fixed way. Keep the general exploratory view reachable from every purpose-keyed one.

Variants

The variants differ by purpose — each serves one of the recurring information behaviours the actor brings back to the same collection.

Analytical exploration

Draw conclusions through structured investigation. Medium granularity with comparison, filtering, and grouping; the actor explores, tests hypotheses, generates insights. Typically a collection framing with flexible refinement and several representations to switch between. This is the least зurposeful of the three — little more than the general view with sensible presets — because exploring is the one purpose that pre-curation harms rather than helps. It is also the view the other two must keep reachable.

Monitoring

Maintain operational awareness without deep investigation — answer “is anything wrong?” in passing. Aggregate metrics, trends, and status indicators rendered as compact summaries; typically a zoomed-out collection framing with auto-refresh.

Drilldown investigation

Chase one concern to its bottom, ending at an individual item’s full view.

From watch to chase

Monitoring exists to hand off: something changes or catches attention, and the watch becomes a chase. When the purpose recurs on a rhythm — the views along that path can be staged. Each tier is designed for the attention budget of its own moment. Deeper tiers never push themselves forward; the actor moves inward deliberately. That makes the outer tier’s selection consequential: whatever it omits, the actor must know to ask for. The outer tier is often shared across the team, with room for personalisation increasing inward.

The hinge between watch and chase is clearest when it is rule-based. Where the domain can state its detection rules explicitly, the watch becomes a checklist of detected problems, and selecting one starts the chase with the reason attached — problem-curated view.

Resources & references

• Zhang, Ehrmann, Mazwi, Eytan, Ghassemi & Chevalier (2022) Get to the point! Problem-based curated data views to augment care for critically ill patients — In-Sight: the ICU study behind the graduated tiers; the problem-curated form it introduced lives at problem-curated view
• Sarikaya, Correll, Bartram, Tory & Fisher (2018) What do we talk about when we talk about dashboards? — splits the visual genre from the functional one; design principles do not transfer between them
• Pauwels et al. (2009) Dashboards as a service — metrics must be interconnected, not merely co-located
• Роман Бунин — Dashboard is dead. Long live dashboard! — separate operational reporting from exploratory analytics
• Роман Бунин — Шаблоны верстки дашбордов — despite the title, keyed by task, not geometry (“I divide dashboards by the task they solve”); the three templates — entity page, analytical tool, приборная панель — corroborate this carving from practice, and it is the monitoring one that keeps the name
• Александр Бараков — Dashboard, dashboard - Сколько тебе жить осталось? — the stagnation diagnosis and the successor forms: pinboards, role presets, generated views