Introduction
The Ather Rizta is Ather Energy's family scooter. Since its April 2024 launch it has become the company's volume driver, crossing three lakh units in about two years, and it pulled Ather beyond its original buyer: the young, tech-forward commuter who chose the 450X for performance. A Rizta household looks different. One scooter is often shared by a husband and wife, an adult child going to college, and sometimes a parent who rides to the market. Yet the scooter and the Ather app were designed around a single owner with a single phone.
The prompt asks us to design multi-rider family profiles for the Rizta and the Ather app. This is a product design question with hardware, software and safety constraints. I'll clarify scope, explain why this is worth building, choose a target segment, map pain points, propose and prioritise solutions, and close with success metrics.
Open by confirming the frame out loud: "I'll design for a single Rizta shared by two to four people in one household, across the scooter dashboard and the Ather app. Is that the right scope?"
Step 1
Clarify Questions (3 minutes)
- Why it matters: The 450 series skews toward single-owner enthusiasts; the Rizta skews toward families.
- Hypothetical answer: Start with the Rizta Z (with the 7-inch touchscreen and AtherStack), then extend to the 450 line.
- Impact: We can assume a touchscreen dashboard and recent AtherStack software, which removes a hardware constraint.
- Why it matters: A safety-led design looks different from a monetisation-led one.
- Hypothetical answer: Primary goal is to make the Rizta the obvious "family scooter" and raise daily usage and app engagement across all household riders. Upsell to the Pro Pack is secondary.
- Impact: We optimise for number of active riders per vehicle, not revenue per user.
- Why it matters: Identity drives every personalised feature.
- Hypothetical answer: Today the scooter pairs with the owner's phone over Bluetooth; there is no rider recognition.
- Impact: Rider identification becomes a core design problem.
- Hypothetical answer: Data must follow India's DPDP Act; any rider over 18 should control their own ride history.
- Impact: We need consent-based sharing, not silent tracking.
Propose the Goal
Let every person in a Rizta household ride with their own settings, see their own rides and feel safe, while the owner keeps control of the vehicle. Success means more distinct active riders per scooter and higher weekly app engagement from non-owner riders.
Define the Scope
In scope: rider profiles, rider switching on the dashboard, permissions in the app, personal ride modes and safety alerts. Out of scope: insurance pricing, financing and changes to the motor or battery hardware.
Say what is out of scope. It shows you can protect engineering capacity, which matters at a hardware company where firmware and app teams share release trains.
Practice similar questions
Subscribe to access the full answer