Product Sense: Build a Facebook Product for Kids, From Target Age to Safety Metrics

You are a product manager at Facebook and have been asked to design a new service for children. Decide who it should serve and what it should do, take the design from the user problem to a first version, and explain how you would know it is succeeding. ```hint A children's product has more than one user Children rarely choose or control the apps they use, and a product for them operates under rules that adult Facebook products do not. Decide early whose problem you are solving and what the service must never do. ``` ### Clarifying Questions - Which ages count as children here: kids below Facebook's minimum account age of 13, teenagers, or both? - What is the goal for Meta: bringing families closer, building a future audience, or a new business line? May the service carry ads or charge a fee? - Should this be a standalone app for the child, a feature parents use inside Facebook, or both? - Which countries are in scope, given that rules on children's data differ by market? ### What a Strong Answer Covers - A goal tied to Meta's mission and a clear reason a children's service is worth the risk. - Segmentation by age and by the adults around a child (parents, relatives, educators), with a justified target. - Specific pain points and solutions, prioritized into a defined first version. - Success metrics that reward healthy connection rather than time spent, with safety and trust guardrails. - Child safety, privacy, regulatory and reputational risks, each with a concrete mitigation. ### Follow-up Questions - Parent groups publicly object to the launch. How do you respond, and what would you change? - What should happen when a child using the service turns 13? - Leadership asks how this service makes money. What is your answer?