Product Design for a Child-Safe WhatsApp Messaging Experience

As a product manager at Meta, design a version of WhatsApp for children. Explain who the product serves, which of their problems it should solve first, what you would build, and how you would measure whether it works. ```hint Two users, one product A messaging product for children has a child who must want to use it and a parent who must trust it. Consider how WhatsApp's phone-number accounts and end-to-end encryption shape what kind of oversight is possible. ``` ### Clarifying Questions - What age range counts as children here: below WhatsApp's minimum age, younger teens, or both? Consent rules differ sharply between those groups. - Is this a separate app, or a child mode within WhatsApp that is linked to a parent's account? - Who is the primary customer: the child who uses the product every day, or the parent who decides whether to allow it? - Should parents be able to read their child's messages, or only see contacts and usage, given that WhatsApp chats are end-to-end encrypted? ### What a Strong Answer Covers - A defined age range and a goal that fits WhatsApp's purpose of simple, private messaging. - The needs of both children and parents, with a reasoned choice of whom to design for first. - Safety design: who can contact the child, how approvals work, and how parental oversight coexists with encryption. - A prioritized MVP and later features, with a success metric and guardrails. - Risks including child-privacy law, misuse by approved contacts, and the move to a regular account as the child grows up. ### Follow-up Questions - A classmate the parent has not approved adds the child to a group chat. What should happen? - Parents ask to read every message. How do you weigh that against the child's privacy and encryption? - How would you keep the product from pushing children toward compulsive use?