Shipment & Exception Control Tower
A representative control tower for a European road network: live shipment monitoring, exception management and route tracking, run on wall displays and analyst workstations.
- Product
- Freightline Control
- Platform
- Enterprise web application
- Role
- Product designer - data visualisation, alerting model, dark-environment interface design
- Design focus
- Data visualisationAlerting modelOperational decision-makingControl-room ergonomics
Problem
Everything was an alert, so nothing was. Weather notices, customs holds and carrier no-shows arrived in the same feed with the same weight.
Even once a disruption was understood, resolving it meant knowing the informal playbook a senior controller carried in their head.
- 09:12Weather notice - Rhine corridor
- 09:14Customs hold - SHP-40218
- 09:15Driver break logged
- 09:17Carrier no-show - Duisburg hub
- 09:19Temperature reading nominal
- 09:21ETA revised - SHP-40144
Same weight, same colour, same position - severity had to be inferred.
Approach
- 01
Built a severity model before any pixels
Worked with controllers to define what makes an exception critical: SLA exposure, downstream loads and time remaining. The interface renders that model rather than inventing its own hierarchy.
- 02
Designed for a dark control room
A dark surface with a single accent, low-chroma neutrals and heavier hit areas - legible from across a room and comfortable across a twelve-hour shift.
- 03
Turned tribal knowledge into playbooks
Each exception type carries a recommended action drawn from what experienced controllers already do, presented as a suggestion the controller accepts or dismisses.
Key UX decisions
One accent colour, reserved for critical
In a dark environment colour reads as urgency. Only genuinely critical states use the accent; everything else is expressed in neutral weight.
Delay measured in minutes by hub, not by shipment
Controllers act at hub level. The primary chart aggregates delay where intervention happens, with shipment detail one click away.
Impact stated before the action
Route tracking shows linked orders, downstream loads and SLA window remaining, so the cost of doing nothing is visible next to the decision.
Timeline over map as the default detail view
The question in an exception is what happened and when. The chronology leads; geography supports it.
Final product screens
Outcome & impact
Exceptions arrive ranked by operational consequence rather than by arrival time, and each one carries a recommended next step.
The severity model and dark interface language were documented as a reusable pattern for other real-time surfaces in the network.
Some product names, data, and details have been anonymized or represented for confidentiality. The case studies reflect real design challenges, decisions, workflows, and outcomes from my professional experience.
Recommended action
Reassign to standby carrier
More case studies
All case studies →- 01Insurance
Claims & Policy Operations
Claims handlers worked across disconnected screens to judge cover, chase documents and route approvals - so decisions stalled long before anyone had all the facts.
View case study→ - 02Banking
Transaction & Reconciliation Platform
Operations teams reconciled thousands of ledger and statement lines a day, but the exceptions that actually needed a human were buried inside everything that matched automatically.
View case study→ - 04Enterprise mobile
Field Operations App
Field engineers captured work on a mobile app built like a desktop form - slow to complete, unusable with gloves, and dependent on a connection they often did not have.
View case study→
Let's talk.
I'm Pavan, a Lead Product Designer with six years in enterprise and B2B product design across finance, banking, insurance, logistics and internal business systems. Most of my work sits where business rules, user needs and technical constraints meet. I turn complicated workflows into products that are clear to use and easy to learn.
What I specialise in
- Enterprise & B2B product design
- UX architecture & workflow design
- Interaction & UI design
- Design systems & governance
- UX research & usability testing
- WCAG 2.1 AA accessibility
Availability - open to Lead Product Design and UI/UX roles
- pavanps583@gmail.com
- Phone
- +91 94497 22598
- linkedin.com/in/pavan-ps
- Location
- Mangalore, India