Success Metrics and North Star for the Google Maps Biking Experience

You are a product manager working on Google Maps. Set goals for the experience Maps offers people who get around by bike: define what success should look like for these riders and for the product, and choose the metrics you would use to track progress toward it. ```hint Start from a good ride Picture a successful bike trip from the rider's side, from choosing a route to arriving, and only then turn each part of it into something Maps can measure. ``` ### Clarifying Questions - Does "bikers" mean bicycle riders, motorcycle and scooter riders, or both? Their needs and main markets differ. - Are these goals for a biking experience Maps already offers, or for launching a new one? - Should the goals be a long-term north star for the product or targets for the next planning cycle? - Which markets matter most: cities with heavy bicycle commuting, or countries where motorbikes and scooters carry much of the traffic? ### What a Strong Answer Covers - A goal that follows from what Maps is for and what riders need, with a chosen focus segment. - A north-star metric that reflects value delivered to riders rather than raw usage, and why it beats the alternatives. - Supporting metrics across the ride journey: adoption, retention, route quality and satisfaction. - Guardrails for rider safety, distraction and other travel modes, plus how riders are identified in the data. - How targets are set from baselines and how conflicts between metrics are handled. ### Follow-up Questions - Completed bike trips are growing, but riders rate the routes lower. What could explain this, and what would you do? - Maps never sees crashes directly. How would you tell whether its bike routes are becoming safer? - How would your goals change for motorcycle and scooter riders in markets where two-wheelers dominate traffic?