Meta Product Sense: Choosing and Designing a Money Management Product

You are a product manager at Meta. Design a product for personal finance. Explain why Meta should build it, which users it serves, which money problems it solves first, what the first version includes, and how you would measure success. ```hint Find Meta's right to win Banks and budgeting apps already cover many money tasks. Before choosing users or features, decide what Meta has that those players lack, and let that advantage pick the problem you solve. ``` ### Clarifying Questions - Is the goal engagement in Meta's apps, a new revenue stream, or a foundation for payments and commerce later? - Should the product be a standalone app or part of Facebook, Messenger, Instagram or WhatsApp? - Which market should it launch in first, given that payment systems and financial regulation differ by country? - May the first version hold or move customers' money, or should it avoid becoming a regulated financial service at launch? ### What a Strong Answer Covers - A motivation that fits Meta's strengths and confronts its trust problem with money and personal data - A focused user segment and money pain points ranked by severity and frequency - Solutions tied to those pains, a prioritized MVP, and a reasoned choice of where in Meta's apps the product lives - Success metrics based on completed money tasks rather than time spent, with privacy, fraud and scam guardrails - Regulatory, privacy and safety risks, and how the design handles each ### Follow-up Questions - Users ask whether their financial data will be used to target ads. What is your policy, and what does it cost the business? - Three months after launch, many people try the product once and never return. What do you investigate first? - How would your design change between a market with a widely used instant bank-payment system and one without?