Snapchat Metrics: North Star and Guardrails for Snap Map

Snap Map is the map inside Snapchat where people can see friends who share their location and browse public Stories posted from places around the world. How would you measure its success? ```hint Name the jobs first Decide which jobs the map does for its users before choosing one number to lead with, and remember who has to share something for the map to be worth opening. ``` ### Clarifying Questions - Should I measure Snap Map as a whole, or one part of it, such as friend location sharing or public Stories on the map? - Is success judged by use of the map itself, or by what it adds to Snapchat overall, such as more chats and Snaps between friends? - Is there a decision behind this, for example whether to invest more in the map or to explain a recent change in its usage? ### What a Strong Answer Covers - The map's goal, tied to Snapchat's mission and to the user jobs it serves - A north-star metric that reflects real value, with reasons it beats simpler counts such as opens - Input metrics across reach, the supply of shared locations and Stories, engagement and retention - Guardrails on privacy and safety for a location feature, plus product health and cannibalization - Segmentation, and a way to show causality such as experiments or holdouts ### Follow-up Questions - After a redesign, map opens rise sharply but conversations started from the map stay flat. How do you read that? - How would you tell whether location sharing is making some users feel less safe, and what would you do about it? - The north-star metric drops for two weeks. How would you find the cause?