Product sense: what a smartphone should be when its user is six years old

You are a product manager asked to design a smartphone whose user is a six-year-old. Explain who the product is for, what problems it should solve, what you would build, and how you would know it is working. ```hint Separate the roles Before listing features, sort out who uses the phone, who buys it and who controls its settings, then decide whose need the first version must meet. ``` ### Clarifying Questions - Must the result be new hardware, or would a locked-down configuration of an existing phone count? - Is a wearable form factor acceptable if it meets the same needs, or should it stay a handheld phone? - Which market is the child in, and how much time do children that age typically spend away from a parent or caregiver there? - Is the business goal to earn money on the device itself, on an ongoing service, or mainly to reach a new group of customers? ### What a Strong Answer Covers - A stated goal for the product and the difference between the child as user and the adult as buyer - Segments of families or situations compared, with one chosen and the reason - Prioritized needs for that segment, including what the phone should deliberately leave out - Design choices matched to a six-year-old's reading, dexterity and attention, plus the controls the adults get - Success metrics with guardrails, and the risks around privacy, safety and screen time ### Follow-up Questions - How would you price and sell a device the child will outgrow within a few years? - What would you test with families before committing to custom hardware? - How would you handle the location data and recordings the phone collects about a child?