Shared-scooter customer app: choose users, map trip needs, scope a first release

You are a product manager at a scooter-sharing business, asked to design the app its customers will use. Work out who the app serves and what it should achieve, choose which users to design for first, map what they need from the app, propose and prioritize features for a first release, and explain how you would measure success. ```hint Settle the business first Pin down how the business supplies its scooters before choosing features: that answer decides which kinds of users the app has to serve and where a trip is most likely to go wrong. ``` ### Clarifying Questions - Does the business run its own fleet, or does it connect private scooter owners with people who want to rent a scooter or ride along? - Are the scooters one-person electric stand-up models or seated two-person scooters? - Where does the service launch first, and which local rules on parking, rider age and helmets apply there? - Is this a new service, or are there already scooters on the street and existing riders? ### What a Strong Answer Covers - A defined business model and goal for the app, and the user groups that model implies - User segments compared, with a primary one chosen and the reason for the choice - Needs traced across a full trip, from finding a scooter or ride to ending the trip and paying, ranked by severity - Features prioritized into a first release with explicit criteria, including their effect on safety and on people who never use the app - A primary metric with guardrails, plus the main risks and how to mitigate them ### Follow-up Questions - How would the app discourage riders from leaving scooters where they block sidewalks, and how would you know it worked? - Which parts of your design change if the business switches between owning its fleet and connecting private owners with riders? - What would you pilot first, and what result would make you stop?