Meridian
A logistics control room reorganized around alert severity, operator focus, and fast decisions.
Operational design
- Prioritized exceptions by operational impact instead of displaying every event with equal weight.
- Kept route context, ownership, and next actions together while operators investigated an alert.
- Specified dense-table, filter, alert, and empty-state patterns for large and small screens.
Case study
Challenge. Dispatch teams monitored thousands of shipments through dashboards that gave routine updates and critical exceptions the same visual weight. Resolving an alert meant opening multiple views and reconstructing context by hand.
Approach. I shadowed operators across busy shifts, catalogued alert types, and mapped the decisions attached to each severity level. Low-fidelity control-room prototypes helped us test density, scanning order, filtering, and handoff between operators.
Outcome. The new workspace centered the exception queue, preserved route context during investigation, and surfaced the next available action. A responsive dashboard specification documented behavior for tables, maps, alerts, filters, and degraded data states.
Before & after
An undifferentiated event dashboard became an exception-led control room where severity, route context, ownership, and the next operational action are immediately scannable.
#C2410C → #F97316#0F766E#FEF3C7#17202AColor library
Orange elevates time-sensitive exceptions, teal distinguishes stable operational states, and pale amber supports warnings without overwhelming the control room. Charcoal keeps dense routing information crisp and scannable.
Font library
DM Sans keeps the control room compact and readable across tables, filters, and alert queues. Space Mono gives routes, timestamps, and shipment identifiers a consistent operational rhythm.