Lyft Default Pickup Pin: Setting Goals, a North-Star Metric and Guardrails

You are a product manager at Lyft responsible for the default pickup location pin, the pin that marks where the rider will be picked up before the rider adjusts anything. Define the goals of this feature and the metrics that would tell you whether it is succeeding. ```hint Judge the pin by the pickup A rider confirming the pin quickly is only half the story. Think about what happens later in the trip that shows whether the default spot was actually a good place to meet the driver. ``` ### Clarifying Questions - How is the default chosen: the rider's raw GPS position, a nearby spot the app snaps to, or a pickup location the rider saved earlier? - Is this a new launch, where adoption matters most, or an existing feature whose quality we want to improve? - Should the goals cover drivers as well, or only the rider's booking flow? ### What a Strong Answer Covers - A clear definition of the feature and how it serves Lyft's aim of fast, reliable pickups - Goals for riders, drivers and Lyft, tied to the journey from opening the app to the trip starting - A north-star metric that reflects pickup quality, not just whether riders accept the default - Supporting metrics for speed, accuracy and pickup friction, plus guardrails - How to measure the effect causally and which location types and conditions to segment by ### Follow-up Questions - After a change, riders accept the default pin more often, but rider-driver calls before pickup also rise. How do you read that? - How would your metrics differ at an airport with a designated pickup area compared with a suburban street? - How would you design an experiment comparing two ways of choosing the default pin?