Facebook Product Sense: Inventing a Music Product, Its Audience and Its Success Metrics

As a product manager at Meta, you are asked to come up with a brand-new way for people to enjoy and engage with music on Facebook. The prompt leaves everything open: choose the goal, the audience and the problem to solve, describe the product you would build, and explain how you would know it is working. ```hint What Facebook has that music apps lack Streaming apps already play music well. Think about what Facebook brings that they do not, such as friends, Groups, Events and artists' Pages in one place, and which music problems get better because of it. ``` ### Clarifying Questions - Is the goal more engagement on Facebook, new revenue, or better tools for artists, and how will the team judge success? - Should the experience serve listeners, artists, or the wider music business such as labels, venues and promoters? - Is the scope the main Facebook app only, or can it reach into Messenger, Groups, Events or Meta's VR headsets? - What can be played under current music licensing: full tracks, short clips, or only playback through a partner streaming service? ### What a Strong Answer Covers - A goal tied to Facebook's mission of connecting people, with a reason a music product serves it. - A deliberate comparison of user groups (listeners at different levels of engagement, artists, industry) and a single segment chosen with justification. - Specific pain points for that segment that existing streaming services do not solve well. - Several solution ideas prioritized by impact and effort, with one developed into a concrete experience. - Success metrics with guardrails, plus risks such as licensing cost, cold start, and competition with established streaming apps. ### Follow-up Questions - Music streaming apps already have social features. Why would someone use yours instead? - After launch, people try the feature once and do not come back. How would you find out why? - How would licensing costs change what you build first?