Shazam Success Metrics: North Star, Recognition Funnel and Guardrails for a Music ID App

Shazam is an app that identifies a song from a few seconds of audio picked up by the device's microphone and lets the user act on the result, for example by playing the full track in a streaming service. How would you measure whether Shazam is successful? Define what success means for the product, then choose the metrics you would track and explain why each one belongs. ```hint Find the moment of value What does a user need to get out of a single use of Shazam, and what would they do right afterward if it worked well? Build the metrics around that moment rather than around time spent in the app. ``` ### Clarifying Questions - How does Shazam create value for its owner in this scenario: ad revenue, payments for sending listeners to streaming services, or support for the owner's own music service? - Does "Shazam" mean the mobile app only, or also ways to identify a song without opening it, such as widgets and shortcuts? - Is this an overall health check of the product, or a goal for a specific team or launch? ### What a Strong Answer Covers - The product's mission and the user's core job, stated before any metric - A user journey from attempting a recognition to acting on the result, with metrics at each step - One north-star metric with a clear rationale, supported by acquisition, engagement, retention and business-value metrics - Guardrails specific to recognition, such as match rate, speed and wrong matches - Awareness that Shazam is used in short, occasional bursts, which makes some standard engagement metrics misleading ### Follow-up Questions - Why might time spent in the app be a poor success metric for Shazam, and what would you use instead? - Weekly recognitions fall while installs stay flat. How would you investigate? - How would you measure the value Shazam creates for the streaming services it sends listeners to?