Build a Goal-Driven Feature Roadmap for Meta's Messenger App

You are a product manager on Messenger, Meta's standalone messaging app for one-to-one and group chats, calls and media sharing. The team is planning the next version of the app. Explain how you would decide which features go into it, and what you would prioritize. ```hint Let the goal pick the winners Agree on the single outcome this release should move and the group of users it serves before listing any features; the same feature can rank first or last depending on that choice. ``` ### Clarifying Questions - Is there a company goal this release must serve, such as growth among younger users, deeper group use, or trust and safety, or should I propose one? - Which platforms are in scope: the phone apps only, or also web and desktop? - How large is the team and how long is the release cycle, so I can judge what fits? - Are features that connect to other Meta apps, such as Facebook groups or Instagram messaging, in scope? ### What a Strong Answer Covers - A stated goal and success metric for the release, justified by Messenger's position among other messaging apps - A chosen user segment and its concrete messaging pain points - A candidate feature list derived from those pain points and checked against what Messenger already offers - A transparent prioritization method, such as reach, impact, confidence and effort, applied to the list and then adjusted for dependencies, risk and strategic fit - A final ranked roadmap that names what is deliberately cut and how each top item will be measured ### Follow-up Questions - End-to-end encryption limits what the server can read. Which of your top features become harder to build, and does that change your ranking? - Your top feature wins its experiment on engagement but increases reported spam. Do you ship it? - If leadership halves the team, which items survive, and why?