Product Sense: How Facebook Could Help People Plan Weddings

Meta wants Facebook to help people who are planning a wedding. As a product manager, design that experience: explain why it is worth building for Meta, decide whom it serves, choose the problems it solves first, describe what you would build, and say how you would judge whether it works. ```hint Map the planning journey Write out what has to happen between an engagement and the wedding day, then look for the step that hurts most today and where Facebook's network and existing tools give it an edge over a standalone wedding app. ``` ### Clarifying Questions - Is the main goal deeper engagement on Facebook, revenue from wedding businesses (ads, leads or transactions), or both? - Which participants are in scope: the couple, family and friends who help, guests, or the businesses that serve weddings? - Does the experience live only in the Facebook app, or can it use Messenger, Instagram and WhatsApp as well? - Which markets are we designing for first, given how much wedding customs and the businesses involved vary between cultures? ### What a Strong Answer Covers - Why Meta would invest in this, tied to an explicit goal - The people involved in a wedding compared, with one group chosen and the reason - Pain points across the planning journey, ranked, with a focus chosen - Solutions that build on what Facebook already has, prioritized with explicit criteria, and a scoped first version - Success metrics with guardrails, and the main risks, including privacy around a personal life event ### Follow-up Questions - How would you launch in a new city so that the product is useful to the first couples who try it, before many others are using it? - Most people plan a wedding once. How would you justify the investment, and what keeps the product useful after the wedding? - How would you keep the experience from feeling intrusive, for example toward friends who are not invited or a couple whose plans fall through?