Reducing Post-Assignment Cancellations in DriveU Scheduled Rides
Why occasional DriveU users cancel scheduled rides moments after a driver is assigned, and how to stop it
✳The problem they went after
Occasional DriveU riders book a scheduled trip, see an ETA after the driver is assigned, and read it as how long they are waiting right now rather than a pickup set for later. Confusion turns into anxiety, anxiety turns into a cancellation, and driver utilisation suffers alongside the experience. Nothing here is about price or driver quality; the product is simply failing to communicate state.
✳What they actually did
A why-why walkthrough breaks the failure into four parts: ambiguous ETA wording, no visual difference between immediate and scheduled rides, no lifecycle visibility, and no explanation of what happens next after assignment. Ten ideas were scored with RICE and collapsed into a single Post-Driver-Assignment Clarity Module. Scheduled rides show a fixed pickup time instead of a generic ETA, a timeline highlights the current state across Assigned, Scheduled, En Route and Arriving, an information card explains the wait, and an action panel offers modify, contact driver or support.
✳What you can take from it
Worth stealing
- Why-why analysis pins the failure on ETA ambiguity
- Ten ideas narrowed by RICE into one coherent module
- Lifecycle timeline: Assigned, Scheduled, En Route, Arriving
- Modifications-to-cancellations ratio as a secondary metric
Read this if
Chasing drop-offs that look behavioural but turn out to be copy problems
The transferable bitA cancellation spike looks like a supply or pricing problem until you notice users are reacting to a number they have misread. Also note the secondary metrics: driver contact within five minutes and the ratio of modifications to cancellations both test whether anxiety found a better outlet.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
