PipThePilot
A six-year-old asks why planes fly. The teacher doesn't need an answer machine — they need a briefing.
- Gemini API
- Human-in-the-loop workflow
- Instructional design
The classroom problem
A six-year-old asks why planes fly, on no notice. Early-childhood teachers train in child development, and aerodynamics sits outside that. “It’s magic” teaches nothing, and a half-remembered answer about air moving faster over the wing plants a misconception someone un-teaches later. The content is simple — lift against gravity. The gap sits between the person having the conversation and the person holding the content.
The design decision
Brief the teacher. A tool that answers the child directly takes the adult out of the exchange that matters, and the follow-up question is the whole lesson. The adult has to stay in the room.
So the output is a thirty-second briefing: the one true idea in words a six-year-old has, the explanation to steer around, and two questions to ask back. The teacher does the talking.
How it works
It doesn’t, yet. The prototype is a chatbot the child types into — built first, reconsidered after. The teacher-facing version exists as a design. Calling that finished would be the easy lie.