Product Design Case: An App That Helps Kids' Field Trips Run Smoothly

You are asked to design an app built around children's field trips. Decide whom the app serves, which problems it solves before, during and after a trip, what goes into the first version, and how you would measure whether it succeeds. ```hint Map everyone on the trip A field trip involves more people than the children on it: whoever organizes it, the adults supervising on the day, the families at home and the place being visited. Decide whose problem to solve first, keeping in mind what young users can and cannot do in an app. ``` ### Clarifying Questions - What age range does "kids" mean here: young primary-school pupils, middle schoolers or teenagers? The answer changes whether the children can have their own phones and accounts. - Is this for school trips organized by teachers, or also for camps, clubs and family outings? - Should the app be standalone, or build on existing Meta products such as Groups, Messenger or Messenger Kids? - Is the main aim smoother logistics and safety, or a richer learning experience at the destination? ### What a Strong Answer Covers - A clear goal and a reasoned choice of primary user among students, teachers, chaperones, parents and venues, given the children's age and what accounts they can hold. - Pain points across planning, the trip day and follow-up, with features mapped to each. - A prioritized, focused first version, including what is deliberately left out. - Success metrics with guardrails, especially for safety and children's privacy. - Risks specific to children: consent, location data, photos of minors and legal limits on collecting children's data. ### Follow-up Questions - How would you get schools to adopt the app when trips are planned by individual teachers with little budget or IT support? - Parents want live photos of their children during the trip. How would you handle that request, given privacy and consent? - What would change if the trip were for high-school students who all carry phones?