Lyft Rider Experience: Improving the Pickup Spot the App Suggests by Default

You are a product manager at Lyft, and your team owns the pickup location the app proposes by default when a rider requests a ride. How would you improve it? ```hint Follow the meetup Trace a ride from the moment the app proposes a spot to the moment the rider gets in the car, and look for where that default makes the rider and driver lose time or miss each other. ``` ### Clarifying Questions - Is the default the rider's raw GPS position, a nearby point the app snaps to, or both, and which parts does my team control? - Is the main goal faster pickups, fewer cancellations, fewer calls and messages between rider and driver, or something else? - Should I treat all pickups, or focus on hard places such as airports, stadiums and dense downtown blocks? - Is the driver's side in scope, for example where a car can legally stop and which direction it approaches from? ### What a Strong Answer Covers - A definition of a good default pickup spot for both rider and driver, and a goal metric that reflects it - A diagnosis of the ways defaults fail, such as GPS drift, the wrong side of the street, places a car cannot stop and large venues - Solutions spanning location data, map rules and the rider-facing design, prioritized by impact and effort - Success metrics with guardrails such as walking distance and request conversion - A rollout and experiment plan that handles areas with little history, accessibility needs and safety ### Follow-up Questions - How would you detect from trip data alone that a particular default spot is bad, without anyone reporting it? - A better spot sometimes means asking the rider to walk a couple of minutes. How do you decide when that trade is worth it? - How would the approach change at an airport, where the airport sets the pickup zones?