Teams collect exceptions from spreadsheets, carrier portals and email. A signal without priority and ownership quickly becomes cost.
Independent case study05 / 07Self-initiated concept
SaaS product interface
Morrowlane
Shipment risk becomes a queue of clear actions.
Working frontend prototype
Project in brief
I designed an operational interface for shipments, exceptions, ownership and carrier analytics.01
Project context
Logistics operators, carrier managers and supply-chain leaders.
My goal was to connect risk, exception and next action inside a calm enterprise interface.
Concept scope
These are prototype parameters and coverage, not business results.5access roles
3risk levels
1 queueoperations centre
02
Three key decisions
Each decision connects the product need, human behaviour and interface form.
A queue, not a dashboard
I begin with exceptions, owner, response deadline and next action instead of decorative charts.
Explain the risk
Every signal exposes ETA, route leg, SLA and data freshness.
Keep the context
Lane, carrier and period filters persist across operational views.
03
What I built
Every capability is labelled clearly: what works in the browser and what remains a designed proposal.
01Shipment register and filtersWorking prototype
02Exception queueWorking prototype
03Lane analyticsWorking prototype
04Predictive ETA, SSO and billingDesigned proposal
04
Working artefacts
Not decorative screens, but the logic supporting the product journey.
Role matrix
Risk-score model
Audit-event taxonomy
Limitations
What to know before opening the demo
The prototype has no live transport data, trained model, backend, authentication, SSO or billing. The risk score demonstrates a structure, not a working prediction.
05 / Interactive prototype
Open prototype↗Open English prototype
Explore the core journey and interface behaviour. This is a demonstration build - entered data is not submitted anywhere.
Next case study
06ЛедографEditorial platform→