Lyft advance ride booking: feature design and launch plan

You are a product manager at Lyft. Design a feature that lets riders book a ride for a future date and time, then prepare the go-to-market strategy for launching it. ### Clarifying Questions - How far ahead should riders be able to book, and should every ride type be schedulable at launch? - Is the main goal to win trips riders now book with taxis or car services, to increase loyalty among existing riders, or to earn revenue from a scheduling fee? - Which cities are in scope, and do they differ in driver supply at the hours when scheduled rides are likely to cluster, such as early mornings? - Do rival apps already offer advance booking in the launch markets, so riders already understand the concept? ### Part 1 — Design the scheduled-ride feature Describe who the feature is for and what they use it for, the rider's booking experience, how Lyft keeps the promise that a car will be there at the booked time, and what changes for drivers, including pricing and cancellation rules. ```hint Work back from the pickup A scheduled ride is worth nothing if no car arrives. Decide exactly what you promise the rider, then design when and how a driver becomes committed to that future trip. ``` #### What This Part Should Cover - Priority use cases and rider segments, with a reason for the first one - The rider flow for booking, reminders, changes and cancellation - The mechanism and incentives that get drivers to show up, with a fallback when none does - Pricing and cancellation rules for riders and drivers ### Part 2 — Prepare the go-to-market strategy Plan how you would bring the feature to market: positioning, which riders and cities to start with, the channels for riders and drivers, rollout stages, internal readiness, and the metrics that decide whether to expand. ```hint Launch where reliability is easiest to prove Choose a first audience and first markets where a late pickup hurts most and where you can best guarantee drivers, so early users become evidence that the feature works. ``` #### What This Part Should Cover - Positioning and the launch audience - A staged rollout with channels for both riders and drivers - Readiness of support, operations and engineering - Launch metrics with explicit go/no-go criteria ### What a Strong Answer Covers - Use cases that tie the feature design to the launch audience - A reliability mechanism that is credible to both riders and drivers - A staged plan gated on evidence rather than a single big launch - Metrics for adoption, on-time fulfillment, incrementality against on-demand rides, and driver experience - Risks such as missed pickups, driver gaming and cannibalization, with mitigations ### Follow-up Questions - A few weeks after launch, many early-morning scheduled rides start late. What do you change first? - Should scheduling carry a fee, and how would you test that decision? - How would you tell whether scheduled rides create new trips or only move on-demand trips earlier?