Facebook Podcast Feature Design: Target Users, Pain Points and MVP

As a product manager at Meta, propose how Facebook should offer podcasts to its users. Decide who the product is for and which problem it solves for them, define what the first version includes, and explain how you would measure whether it succeeds. ```hint Start from what Facebook has Dedicated podcast apps already handle playback well. Ask what Facebook offers that they do not, and which listener or podcaster problem that advantage could solve. ``` ### Clarifying Questions - What is the main goal: more engagement on Facebook, growth for podcasters, new revenue, or winning listeners from dedicated podcast apps? - Does the product cover listening only, or creating and publishing too? Audio-only shows, video podcasts, or both? - Should it live inside the main Facebook app and its existing surfaces (feed, Groups, Pages, Reels), or in a separate app? - May we bring in existing shows from their public podcast feeds, or only content that podcasters publish directly on Facebook? ### What a Strong Answer Covers - A goal tied to Facebook's mission and business, and a clear reason people would use Facebook for podcasts instead of a dedicated app. - A chosen segment of listeners, podcasters or communities, with the specific problems they face today. - Prioritized features and a focused first release that builds on Facebook's existing surfaces. - A north-star metric with supporting metrics and guardrails. - Risks such as moderating long-form audio, rights, weak repeat usage and podcaster adoption, with mitigations. ### Follow-up Questions - Early data shows many episode starts, but most listeners stop within the first few minutes. What would you investigate and change? - How would the design differ for video podcasts compared with audio-only shows? - What would convince established podcasters to publish on Facebook first?