Lavish Curiosity

Guided By Curiosity

Lavish Curiosity
Back to Portfolio

UX Research

UPS Driver Experience Improvement

A driver-centered experience study based on real-world package delivery operations — addressing ORION routing pain, air package workflow, and on-the-road navigation.

Client
Self-initiated case study (informed by real UPS driver experience)
Role
UX Researcher & Service Designer
Year
2025
Tools
FigJam · Figma · Notion · Field interviews
UPS Driver Experience Improvement

Research

Insights came from direct UPS driver experience plus interviews with active drivers. I shadowed a full route, mapped stop-by-stop friction, and catalogued every workaround drivers had built around the DIAD device and ORION routing.

Problem Statement

ORION optimizes for distance on paper, but drivers know things ORION doesn't — locked gates, one-way streets at school hours, dock hours, customer preferences, and Next Day Air commit times. The result: drivers override the route, lose time, and feel mistrusted by the system meant to help them.

User Journey

  • Pre-load: sort packages by stop; air packages mixed in, easy to miss
  • On-road: ORION sequence ignores local knowledge; driver re-sequences mentally
  • Air delivery: 10:30 / 12:00 commit times require deviations ORION doesn't prioritize
  • Navigation: addresses route to the wrong side of large buildings/apartment complexes
  • End of day: manual reconciliation of misloads, missed pickups, undelivered air

Pain Points

  • Air commit times not visually surfaced in the stop list
  • ORION reroutes mid-day without explaining why
  • Navigation drops the driver at the property centroid, not the receiving dock
  • No fast way to flag a stop note ('gate code 4412, after 9am') that survives to the next driver
  • Misloads discovered late in the route, forcing backtracking

Wireframes

Concept wireframes for a redesigned DIAD interface: an Air-First stop list with color-coded commit times, a 'Why this order?' explainer for every ORION change, a driver-owned notes layer that persists across drivers, and a dock-accurate destination pin separate from the address pin.

Recommendations

  • Air-First view: commit-time stops always pinned to the top with countdown chips
  • ORION transparency: every reroute shows the trade-off (time saved vs. air risk)
  • Driver Notes layer: persistent, route-shared, structured (gate code, dock side, customer pref)
  • Dock-accurate pins for commercial stops, validated by the previous driver's actual stop point
  • Pre-load misload scanner that flags wrong-truck packages before the driver leaves the building

Expected Outcomes

  • Reduce missed Next Day Air commits by 40%+
  • Cut end-of-route backtracking time by 15–25 minutes per driver per day
  • Improve driver trust in ORION (measured via post-shift sentiment survey)
  • Lower onboarding time for new drivers via shared route knowledge

Selected Visuals

Driver shadowing & journey mapping
Driver shadowing & journey mapping
Concept wireframes for the DIAD redesign
Concept wireframes for the DIAD redesign

Let's Build Something

Have a project in mind?

Brand identity, UX, websites, apparel, and event experiences — guided by curiosity.

More Case Studies