Theme park mobile app: pick the users, the pain points and the first features

Design a mobile app for an amusement park. Decide whom it serves, which of their problems it tackles first and what it does. ```hint Walk through a visit Trace a day at the park, from arrival to exit, for the people you choose to serve, and note each point where time, money or patience is lost. ``` ### Clarifying Questions - Is the app for park guests, for park staff, or for both? - Is this one park or a chain of parks, and does the park already have an app? - Which matters most to the park right now: guest satisfaction and return visits, in-park spending, or managing crowds and ride capacity? - Can the design change park operations, such as how ride queues work, or is it purely a software product? ### What a Strong Answer Covers - A chosen user segment and the reason for it, compared with the other kinds of people at a park - Pain points across the visit, prioritized by how often they occur and how much they hurt the day - A prioritized feature set with an MVP, noting which features depend on park operations or data the park must supply - Success metrics that balance the guest experience against the park's revenue and capacity, with guardrails - Risks specific to a park: patchy signal and battery life, fairness to guests without the app, and crowding when many guests follow the same advice ### Follow-up Questions - If the app shows everyone where the shortest line is, that line may stop being short. How would you prevent this? - If the park wanted a paid option to skip lines, how would you design it so guests who do not pay still have a good day? - How would you test your first feature in a single park before rolling it out?