Launch Decision: Google Autonomous Rides Designed for Kids and Young Teens

Google is considering a self-driving ride service whose riders would be children younger than 16. Should it launch? Make a call and defend it. ```hint Separate rider and buyer The child takes the ride, but a parent or a school decides whether to use it and pays for it. Work out what each of them needs, and what could go wrong outside the drive itself, before you make the call. ``` ### Clarifying Questions - Should I treat this as an extension of Waymo, Alphabet's existing robotaxi service, or as a new Google-branded product? - Would the child ride with no adult in the car at all, or can a remote attendant or an onboard chaperone be part of the design? - Must the service cover every age under 16, or can I recommend serving only part of that range? - Is the launch limited to cities where robotaxi rides already operate? ### What a Strong Answer Covers - A clear recommendation tied to what Google and Alphabet want from autonomous rides - Parents, children of different ages and schools treated as distinct users and buyers, with their needs and use cases - Safety, liability and trust risks beyond the driving itself, and how the brand risk compares with the upside - A phased plan with success metrics, safety guardrails and conditions for pausing - Alternatives considered, and why the recommended path beats them ### Follow-up Questions - What single incident would make you pause the service, and what would you need to see before restarting? - A school district asks to replace some bus routes with this service. How does your answer change? - How would you decide when to lower the minimum rider age?