Microsoft Product Sense: Web Search Built for Children's Safety and Learning

You are a product manager at Microsoft. Design a search product built for children: pick who it serves, decide what it does differently from a general web search engine, and explain how you would measure success. ```hint Two customers, not one A child types the queries, but a parent or a school usually decides whether the product is allowed on the device. Decide whose needs set the bar for the first release. ``` ### Clarifying Questions - Which ages should it serve: early readers, primary-school children, young teens, or is that my choice? - Is this a standalone product or a child mode built on an existing engine such as Bing, with its index and safe-search filtering? - Will children mostly use it at home, in school on managed devices, or both? - What is the goal for Microsoft: reach with families, a stronger position in education, or a business line of its own? ### What a Strong Answer Covers - A chosen age band and primary user, with the roles of parents and teachers made explicit - The ways general search fails children: unsuitable results, reading level, misspelled or question-style queries, distractions - A prioritized first release that changes ranking, query help and result presentation, not just a content filter - Success metrics tied to the goal, with guardrails for unsafe results and for over-blocking legitimate topics - Child-specific risks: children's privacy law, advertising, filter evasion and the trust of parents and schools ### Follow-up Questions - How would the product change for 13- to 16-year-olds who find anything labeled "for kids" patronizing? - Should the product answer questions directly with a generative AI assistant? What safeguards would that need? - How would you fund or justify the product if you cannot show targeted ads to children?