| name | redesign-an-operational-dashboard |
| category | design |
| description | Redesign an operational dashboard around decisions, trusted metrics, state, thresholds, uncertainty, accessibility, drill-down, and incident use. Use when dense monitoring views fail to support timely action. |
redesign-an-operational-dashboard
When to use
- Use for live service, logistics, finance, safety, support, or production operations.
- Do not use color, averages, or one status score to hide consequential variation.
Procedure
- Observe decisions, roles, time pressure, handoffs, environments, and failure history.
- Define each metric, source, owner, freshness, unit, threshold, uncertainty, and action.
- Organize by user task and consequence rather than data source.
- Show current state, trend, baseline, target, anomalies, missing data, and update time.
- Design alerts, drill-down, comparison, filters, ownership, notes, and handoff.
- Test color independence, keyboard, screen reader, zoom, density, wallboard, and mobile.
- Rehearse incidents and measure decision speed plus error.
Failure plan
- Preserve the known-good view until the redesign proves decision parity.
Worked example
A fleet dashboard replaces one green average with regional capacity, freshness, uncertainty, and actionable ownership.
Done
- A dashboard redesign report records decisions, metrics, definitions, layout, thresholds, uncertainty, interaction, accessibility, and evidence
- Source, freshness, missing-data, color, assistive, incident, drill-down, role, and decision-performance tests verify usefulness
