← All work

The parcel was moving. The tracking wasn't.

How we redesigned cross-border shipment visibility at Quincus, turning seven hubs of disconnected events into one journey that operators, partners and customers could act on.

Role
Senior UX Designer, design lead
Timeline
Jul 2020 to Nov 2021
Team
PM, designers, engineering
Quincus - Track & Trace

My role. Senior UX Designer and design lead for QShip / Shipment Insights. I set the design direction, led the design team, and owned research, information architecture, workflows and interface. I worked with the product manager, engineering and the CPO, mentored the designers on the team, and established our design methodology and standards with senior management.

01. Picture a shipment leaving Singapore on Monday.

By Tuesday it has been picked up, sorted at a hub, cleared for export and flown across the Java Sea. By Wednesday it is through customs in Jakarta, about 900 km and half a dozen handoffs from where it started.

Its tracking page still shows almost nothing.

That page woke up only at the last mile. Everyone downstream paid for the silence differently. Customers assumed the parcel was late. Marketplace partners absorbed complaints for delays they hadn't caused. Support agents chased logistics operators, and operators opened several systems to reconstruct where a shipment had been.

The physical journey was connected. The information wasn't.

Every unanswered status question became a phone call, an escalation or another manual search, and every extra person pulled in to answer it made the gap more expensive.

The journey, before and after: 1 of 7 legs visible, then 7 of 7Before: 1 of 7 legs visible. After: all 7.

02. Three people. One shipment. Three different questions.

Before touching a screen, we went where the questions were being asked. We ran three strands of research, each chosen to answer something the others couldn't.

MethodWithWhat it showed
InterviewsLogistics managers and warehouse supervisorsHow one status question travels: customer to marketplace, to support, to operator
Field observationOperators through their shiftsAnswering a single status call meant switching between several systems while the customer waited on the line
SurveysPeople who used tracking every dayWhich questions came up most, and which numbers people had stopped trusting

One record had to answer three very different questions.

AudienceWhat they needed to know
Logistics operatorWhere is inbound cargo? What is about to miss its SLA? What can I act on right now?
End consumerWhere is my parcel, when will it arrive, and do I need to do anything?
Enterprise partnerCan I give my customers reliable tracking without routing them through support?

Three findings set the direction for everything after.

The missing journey was a customer problem, not an operator one.

Operators could dig upstream events out of internal systems, slowly. Customers and partners saw nothing until the last mile, so they called. The people with the least visibility were the ones generating the work.

Every missing answer became someone else's work.

A tracking page only worked if it settled a question without another person having to investigate. That finding became the most important argument we made on the project (chapter 08).

The journey was split across systems, even for us.

Field observation showed operators answering one status call by switching between several systems while the customer waited on the line. Where the same ETA appeared in more than one place, the values sometimes disagreed.

FindingWhat it changedWhere
The missing journey was a customer problemUpstream milestones became customer- and partner-facing, not operator-onlyCh. 04, 06
Every missing answer became someone's workSuccess measured by support deflection, not engagementCh. 08
The journey was split across systemsOne record and one timeline for every readerCh. 04 to 06

03. Five iterations. One missing insight.

We took the experience through five versions. We used each one to test a hypothesis, and each fixed something while exposing what was still broken.

Every version was judged the same four ways: walkthroughs with operators and warehouse supervisors, task tests on prototypes ("a customer is on the phone; where is this shipment?"), checks against real operational scenarios with ops and support, and design reviews with the PM, engineering and the CPO.

V1. A journey that started too late

The legacy product showed final-mile events and nothing upstream. A shipment could be moving through an airport while its customer-facing status sat still.

V2. More information, less understanding

We brought upstream events into the operator view as lists and tables. The data was finally there, but operators still had to read timestamps and rebuild the route in their heads. Accessible isn't the same as understandable.

V3. Better hierarchy, fragmented history

We reorganised the page around identity, live status and history. The order improved. Custody scans and transport legs still lived in separate sections, so people read the same trip twice.

V4. The map solved location, then exposed the clutter

We made the route map the centre of the page: origin, destination, hub movements and the international flight. For the first time, operators could see where a shipment physically was. Customers and partners still couldn't.

Five iterations, from last mile only to one record for every readerFive iterations, from last mile only to one record for every reader

04. The question that changed the brief.

With V4 in hand, we put the design next to the research. Four versions in, operators could see far more of the journey, but those events still lived in separate places, even for us. The customers and partners making the calls still saw tracking begin at the last mile. The calls came from that gap, not from the screen.

We had built a better view for operators. The people making the calls still couldn't see past the last mile.

We reset the brief as one question: what is the smallest, most dependable record that answers operators, consumers and partners across the full journey? Three principles came out of it, and every later design decision was checked against them.

See the entire journey.

One record connects pickup, hub transfer, airport export, international flight, customs, destination line haul and last-mile delivery. That meant depending on carrier and flight data we didn't control. Where an event was missing, the page had to say so plainly rather than imply the parcel had stopped.

Put live decisions above static details.

The page follows the order an operator investigates in: identity and live lane, then ETA, SLA countdown and ETA confidence, then the activity timeline, then parties, charges, contents and documents. The most time-sensitive facts get the most attention.

Match the call to the shipment at once.

Callers quote an order number, a reference or a company name, not our tracking ID. We put consignee, order and reference in one row at the top of the record, so whoever takes the call can match it to the shipment at once.

That became V5: the map kept as context, and the information architecture rebuilt around what each reader needed to know and do.

The shipment record: V4, map firstThe shipment record: V5, shippedV4, map firstV5, shippedThe same shipment in V4 and V5. Drag to compare. One record, every depth: list, full page, side panel and phoneOne record, every depth: list, full page, side panel and phone

05. One shipment, many forms.

Operators, support and customers meet the same shipment in different places and at different moments. So instead of designing pages, we designed the shipment once, as an object, and gave it a form for each place it appears.

One shipment, many forms: panel, journey, dark mode, the path in four marks, list, phone and mapOne shipment, many forms

One object, a form for every place.

Every object in the product (shipment, exception, leg, party, stop) is one part with a fixed set of fields, drawn in six sizes: a row for lists, a slim line, a medium card, a card for panels and docks, a tag on the map, and the head of a full page. A field never changes its name, format or position between sizes, so a reader who learns it once can read it anywhere.

Rows, not tables.

Earlier versions used tables. Tables invite a column for everything, repeat the same value down the page and break on a narrow screen. Lists became stacked object rows with the same fields as the card, which turn into cards on a phone. A column that would show the same value on every row is hidden.

The right depth for each job.

SurfaceThe jobWhat it showsWhat it leaves out
List rowTriage: which shipment needs attentionID, consignee, lane and progress, ETA, status, SLAParties, legs, documents
Side panelCheck one shipment without leaving the networkIdentity, ETA and SLA target, the journey by leg, shipper and consigneeGoods, paperwork, full history
Full pageSettle a call or fix a problemLive readings, the journey, goods, paperwork, history, the lane on the map, the next stepNothing
Phone cardThe same triage away from a deskThe list row, stackedSame as the list

A small visual language.

Delivery status is always a dot and SLA status always a square. Red means a problem and nothing else, and one blue covers everything you can act on. The path is a thin grey track: grey where the parcel has travelled, a blue dot where it is now, a red dot where it is stuck, hollow ahead, with no step names to read. In colour-blind mode, problem marks also change shape.

One system behind every screen.

Every screen draws from the same small set of decisions: colour tokens with one job each, one typeface (Geist) on a fixed type scale, four spacing steps and five corner radii. Dark mode is built from the same tokens rather than designed twice, so a screen designed once works in both. New screens start from the system, not from a blank page, which kept the product consistent as it grew.

Design system: colour, type, the map, components, menus, journey, motion, spacing and cornersOne system behind every screen The shipment record: LightThe shipment record: DarkLightDarkOne set of tokens, two modes. Drag to compare.

A calm map.

At rest, the network map is quiet: thin grey lanes, small hub dots and their codes. Hovering or selecting a lane lights only that lane in its status colour and fades the rest, with one flat tag for its code, count and status. The selection lives in the link, so an operator can send a colleague exactly what they are looking at.

Motion that informs.

Panels, cards and swaps fade; nothing slides in or out. On the network map, lanes draw in and hubs appear from the centre outward, so the reader sees the shape of the network form. On a shipment page, the route is there on first paint, because the operator came for an answer, not an animation. Nothing loops, and reduced motion is respected. Six timings cover everything, from 100 ms for a hover to 1.4 s for the map.

Rows arrive in order, the network forms, then one lane comes forward.

Accessibility, built into the process.

Field observation showed older operators and colour-blind operators struggling to read the screen through a long shift. So accessibility became part of how we designed, not a pass at the end. A high contrast mode raises label and border contrast and enlarges text. A colour-blind mode makes problem marks change shape as well as colour, so a breach never depends on seeing red.

The shipment record: DefaultThe shipment record: High contrast, larger textDefaultHigh contrast, larger textReadable through a long shift. Drag to compare. The shipment list seen with red-blindness: Colour-blind mode offThe shipment list seen with red-blindness: Colour-blind mode onColour-blind mode offColour-blind mode onBoth sides seen with red-blindness. Breached SLAs turn from squares into diamonds.

Words that do one job.

The interface speaks in plain nouns and facts: "3h 05m late", "Address incomplete", "Resolve exception". No sentence repeats a number already on the screen, no line sits under a title just to fill it, and counts never go inside button labels. An operator scanning a list between calls reads what changed, not what the designer wanted to say.

What we said no to.

  • Pills and badges on every figure, in favour of plain label and value pairs that read in one glance.
  • A large origin and destination headline, in favour of the journey itself, so the next handoff is always in view.
  • A row of action buttons on every record, in favour of one menu, so the record stays the focus.
  • Tables, slide-in panels and soft drop shadows, in favour of object rows, a fade and a single hairline.
What we said no to: pills became figures, a headline became the journey, four buttons became one menuPills became figures, a headline became the journey, four buttons became one menu

06. Turning an event log into a story.

A cross-border shipment is a chain of handoffs between carriers, warehouses, airports and delivery teams. Following it used to mean stitching separate systems together.

The systems hand you two timelines, not one. Shipment milestones come from warehouse and operations tools; flight legs and carrier scans come from another set of systems. Engineering found that split easier to build, so the first design kept them apart: a shipment timeline and a transport timeline, side by side.

It failed in usability testing. Operators kept asking the screen one question, "did this flight cause this delay?", and answering it meant reading both timelines and stitching them together in their heads. A split that was clean for the backend was work for the user. Flight tracking had the same problem: it started on its own page, and operators bounced between two pages to answer one question. So we folded the live flight data into the shipment record as well.

We merged carrier movements and chain-of-custody scans into one chronological timeline. Each event shows who handled the parcel, where, when, its weight, and the flight or vehicle that moved it.

The same history powers a simpler consumer view: clear milestones, none of the operational detail. One record, shown at the depth each audience needs.

That record also became the place work happened, not only where it was looked up:

BeforeAfter
Shipment documents spread across several manual formsOne digital document flow attached to the shipment
Updates scattered across emails and callsShared channels for operators, partners and support on each shipment
One history, every handoffOne history, every handoff

07. The real test was the bad day.

A shipment moving normally needs almost nothing from anyone. A delayed flight, an incomplete address or a missed handoff is where an interface earns trust, so we designed those states first.

A delayed flight shouldn't become a surprise failed delivery.

When a flight slips, the revised ETA and the SLA risk appear together, with Notify consignee right there. The operator can reach the customer before the customer reaches support.

An address exception should end in a fix.

Instead of a generic error, the page shows the incomplete address, a suggested correction from Quincus's address engine, and one confirm action.

Delivery needed a verifiable ending.

Signature, signer and COD collected sit on the same record as the journey, so a team can confirm the final handoff without searching elsewhere.

The bad day, handled: a flight delay raised at 13:02, resolved 18 minutes later, the consignee notified a day ahead of the new ETAA flight delay raised at 13:02, resolved 18 minutes later, the consignee notified a day ahead of the new ETA

08. Changing what success meant.

The brief measured success the usual way: engagement with the tracking page. Research said that was the wrong number. A customer who opened the page five times hadn't been helped; they'd been left waiting. The real cost sat in support, in every call, escalation and manual search an unanswered question created.

So we made the case to the CPO to change the goal from engagement to support deflection: a tracking experience succeeds when people stop needing to ask.

It was the harder metric to sign up for. Engagement comes free with product analytics. Deflection needs support data, and it can't be moved by making the page busier. It also changed what we prioritised. Upstream visibility, exception handling and one dependable record moved to the top, because those were what stopped calls.

Once it was agreed, it became the test for every review with product and engineering: does this answer a question someone would otherwise call about? The reset brief in chapter 04, the merged timeline and the decision to design the bad day first all came from holding the team to that test.

Alongside the work, I mentored the designers on the team and set our design methodology and standards with senior management.

09. What changed after launch.

The evidence comes in three kinds, kept apart: what was measured, what shipped, and what a model suggests it is worth.

Measured

Our internal user satisfaction score, collected through an on-site survey, rose 30% after the redesign. We tracked NPS alongside it as a separate measure. We no longer have the underlying survey data, so we quote the figure as it was reported.

Shipped

BeforeAfter launch
Customer and partner tracking began at the last mileUpstream milestones (export, flight, customs, line haul) visible to customers and partners
Events split across separate views and systemsOne record and one timeline for every reader
Address problems surfaced as generic errorsA suggested fix and one confirm action
Flight delays discovered lateRevised ETA, SLA risk and Notify consignee in one view
Shipment documents across several manual formsOne digital document flow on the shipment
One fixed visual modeHigh contrast with larger text, and a colour-blind friendly mode

Set as the goal, not yet measured

Support deflection was the goal leadership agreed to (chapter 08). We didn't instrument it at launch, so there is no measured deflection figure. The strategic decision stands; the measurement system is what we'd build first next time (chapter 10).

Modeled scenario: what this visibility could be worth to a partner

This is a model, not a measured result. To show the commercial stakes, we modeled a representative cross-border marketplace with 17 support agents. Full method and assumptions are at the end.

Measure (modeled, month six)Change
Status enquiries per 1,000 shipmentsabout 38% fewer
Operator lookup timeabout 57% faster
Support handling costabout US$47,000 a year avoided

10. What we'd carry into the next product.

More data doesn't mean more clarity.

The early versions gave operators more information and still left them rebuilding the journey. The real gain came from unifying the information model and putting each event in context.

Question the scope before polishing the screen.

Several versions improved the page without touching the reason customers were calling. We'd now push on the edges of a problem before the team commits to a screen.

The bad day deserves first-class design.

A delayed flight and a broken address told us more about the product's value than any normal delivery did. They showed exactly where the experience had to support a decision.

Measure from day one.

We made support deflection the goal but didn't instrument it at the start. Next time we'd baseline status enquiries by lane, track event coverage and measure contact rates before rollout, so the impact is measured, not modeled.

Closing thought

A parcel doesn't become visible because its latest status shows up on a screen. Visibility comes from connecting the events, handoffs and decisions behind it, and showing them in a way each person can act on.

The most important thing we redesigned wasn't the tracking page. It was what a shipment record had to explain.

Across the operation: overview, exceptions and why shipments were lateAcross the operation: overview, exceptions and why shipments were late

How the partner impact was modeled

Assumes 68,450 shipments a month, 17 agents, 22 working days and 4,731 non-status tickets a month. Status enquiries fall from 2,548 to 1,574 a month; handling time from 9.4 to 6.4 minutes. At US$15 an agent hour plus US$0.50 channel cost per ticket, cost per status ticket moves from US$2.85 to US$2.10.

Annual saving = (2,548 × 2.85 − 1,574 × 2.10) × 12 = US$47,477, gross, at constant volume, excluding integration cost.

Measure (modeled)BeforeMonth sixChange
Status enquiries per 1,000 shipments37.223.038.2% fewer
Visible before the last mile0%93.4%+93.4 pp
Operator lookup time6.5 min2.8 min56.9% faster
Handling time per status ticket9.4 min6.4 min31.9% faster
Unexplained-delay complaints a month61232147.5% fewer
Parcels re-handled or reported missing a month19412336.6% fewer
Support handling cost a monthUS$7,262US$3,305US$47,477 a year avoided

Sources:

Results
+30%internal satisfaction score after launch
7hubs across South East Asia in one journey
3operators, partners and customers on one record
5iterations from legacy to final
Next case study
How do you close the gap between a powerful AI engine and the people building on it?Building design practice from scratch at an Enterprise AI platform, then rebuilding how design works when AI changed engineering