Uber — 2017 — 2022
Reserve, Dispatch & Marketplace Systems
Scheduling and dispatch mechanics in a live two-sided marketplace.
- Role
- Senior Product Designer
Problem
A ride booked days ahead is a promise made by a marketplace that does not exist yet. No driver is assigned, supply is a forecast, and the rider is making a flight.
Fleet matching and multi-driver dispatch exposed the seam between what a rider was promised and what the marketplace could guarantee. That foundation later unlocked Reserve, Hourly, Intercity, and Rentals.
My scope
- 01Fleet Match, multi-driver dispatch, Reserve, Hourly, Intercity, Rentals, and later identity and rewards surfaces.
- 02Interaction hierarchy for time-critical moments: assignment, arrival, wait, and no-show.
The decision
I framed the experience around two linked commitments: state the pickup promise plainly and make recovery equally clear when the marketplace could not keep it.
Rather than hiding marketplace uncertainty, Reserve committed to a specific window and made the recovery path — reassignment, wait time, refund — visible before it was needed.
On the driver side, I designed scheduled trips as commitments with visible timing and earnings weight, rather than treating them as another queued request.
What shipped
- 01Uber Reserve rider booking, driver assignment, and arrival experiences.
- 02Fleet Match and multi-driver dispatch foundations, followed by Hourly, Intercity, and Rentals experiences.
- 03A shared vocabulary for marketplace certainty used across scheduling surfaces.
Result
- 97%
- on-time pickup for reserved trips
- 2.4×
- reserved trip volume year over year
- 22%
- fewer support contacts per reserved trip
Program metrics from launch reporting.