Teams collect exceptions from spreadsheets, carrier portals and email. A signal without priority and ownership quickly becomes cost.
Project case study5 / 7Self-initiated concept
SaaS product interface
Morrowlane
Shipment risk becomes a queue of clear actions.
I designed an operational interface for shipments, exceptions, ownership and carrier analytics.
Working frontend prototype
1
Task and constraints
Logistics operators, carrier managers and supply-chain leaders.
My goal was to connect risk, exception and next action inside a calm enterprise interface.
Prototype scope
These figures describe concept coverage, not business results.4access roles
3risk levels
1 queueoperations centre
2
Key decisions
Each decision answers a specific product question instead of existing for visual effect.
1
A queue, not a dashboard
I begin with exceptions, owner, response deadline and next action instead of decorative charts.
2
Explain the risk
Every signal exposes ETA, route leg, SLA and data freshness.
3
Keep the context
Lane, carrier and period filters persist across operational views.
3
What you can test
Capabilities marked “Available in the demo” open their exact working screen.
1Shipment register and filtersAvailable in the demoOpen screen2Exception queueAvailable in the demoOpen screen3Lane analyticsAvailable in the demoOpen screen
4Predictive ETA, SSO and billingDesigned, not connectedNo live demo screen
4
Interface foundation
The material behind the product structure, states and logic.
1
Role matrix
2
Risk-score model
3
Audit-event taxonomy
5 / Working prototype
Open English prototype
The core journey works in the browser. This is a demonstration build: entered data is neither sent nor stored.
Next case study
6ЛедографEditorial platform