Atlas
- Product strategy
- UX/UI design
- Design system
- Angular development
- Remote engagement
- 14 weeks
Atlas moves freight for mid-size shippers across four regions. The team ran the operation from four separate dashboards, none of which agreed on where a load actually was, and dispatchers kept a paper notebook to reconcile them.
We embedded with two dispatchers for a fortnight before drawing anything, then worked in weekly slices with their engineering lead reviewing each one. Everything shipped behind a flag, so the old dashboards stayed live until the room stopped opening them.
One live map replacing four dashboards
A decision log the whole team reads
A design system the client extends alone
One live map
Every load, every exception and every driver on a single surface. The map is the application — panels open over it rather than navigating away, so a dispatcher never loses the picture while answering a question about one shipment.
Three decisions
Research turned up only three things a dispatcher does under pressure: reroute, reassign, or tell a customer. Each one is a single control with the consequence stated before it is committed, and each writes to a decision log the whole team reads.
A system they extend alone
Handover was a component library with usage rules and a Figma file that matches the code. Atlas has shipped two features since without us, which is the outcome we were aiming at.
Sample content
They spent two weeks in the dispatch room before showing us a single screen, and it showed. The first prototype already knew things about our operation that took us years to learn.
Dana Whitlock
