Google Maps Strategy: Using Crowdsourced Contributions to Keep Place and Road Data Current

You are a PM on Google Maps. Which strategic pillars would you set so that the information in Maps stays current through what its users contribute? ```hint Not everything goes stale at the same speed A road layout, a shop's opening hours and a crash on the highway age at very different rates, and different people are in a position to notice each change. Ask how that should shape whom you rely on and when you ask them. ``` ### Clarifying Questions - Which data is in scope: changes to the road network, details about places such as hours, closures and phone numbers, or live conditions such as crashes and crowding? - Do business owners editing their own listings count as user-generated content here, or only everyday Maps users? - Is the bigger problem how slowly real-world changes reach Maps, or how often submitted contributions turn out to be wrong? - Should the strategy be global, or aimed first at regions where few people contribute today? ### What a Strong Answer Covers - A definition of freshness that differs by type of data and that can actually be measured. - A small set of pillars spanning how stale data is found, how contributions are gathered with little effort, how they are checked, and why contributors keep coming back. - Concrete initiatives under each pillar, prioritized by how much stale data hurts the people relying on Maps. - Defenses against spam, malicious edits and contributions that are unsafe to make, such as reporting while driving. - Metrics for freshness and accuracy, with guardrails for contributor fatigue and privacy. ### Follow-up Questions - Someone marks a competitor's restaurant as permanently closed. Which of your pillars catches it, and how fast? - How would you keep data current in a region where almost nobody contributes? - You cannot see the ground truth for most places. How would you show that freshness actually improved?