Designing Facebook's First Childcare Product: Scope, Segment and MVP

You are a product manager at Meta, and the company is considering moving Facebook into the childcare space. You have been asked to recommend what to build. What would you propose? Explain which users you would serve, the problems you would solve for them, what you would build first, and how you would measure success. ```hint Pin down what "childcare" means The term spans finding caregivers, coordinating care among family and friends, and supporting parents day to day. Choose the slice where Facebook's existing assets give it a real advantage, and keep in mind who can and cannot hold an account. ``` ### Clarifying Questions - Does "childcare" mean finding and arranging care (sitters, nannies, daycares), coordinating care within a family or community, or supporting parents more broadly? - Should this live inside Facebook, for example in Groups or Marketplace, or as a standalone app? - Is the main goal engagement among parents, a new revenue line, or stronger trust in Meta's products among families? - Which geography should I design for first? ### What a Strong Answer Covers - A reasoned scope for "childcare" and a goal tied to Meta's mission and existing assets such as the friend graph, Groups and Messenger - Segmentation of parents and caregivers, a prioritized segment, and concrete pain points - Several solutions, prioritized with explicit reasoning, and a clearly defined first version - A north-star metric with guardrails for child safety and privacy - Risks specific to children: caregiver vetting, regulation, data protection and parents' trust in Meta ### Follow-up Questions - A caregiver found through your product harms a child. What safeguards should have been in place, and how should Meta respond? - How would you solve the cold-start problem in a city where few trusted caregivers are on the platform? - Would you charge for this product, and how would that change the design?