Uber Lite in One City: Success Metrics for a Low-Bandwidth Ride-Hailing App

You own Uber Lite, the stripped-down version of Uber's rider app, in a city you pick. Which metrics would show whether it is succeeding there? ```hint Why does a lite app exist? Ask what a lightweight app does for riders that the full app cannot, and which riders in your chosen city need that. Your metrics should show whether those riders are actually served, not only whether trips grew. ``` ### Clarifying Questions - Which kind of city should I pick: one where many riders have low-end Android phones and patchy data, or one where most people run the full app comfortably? - Is Uber Lite meant to bring in riders the main app cannot reach, or to give existing riders a fallback when their connection is poor? - Is it newly launched in this city, or established alongside the main app? - Should the metrics cover only riders, or also drivers and the marketplace in the city? ### What a Strong Answer Covers - The purpose of Uber Lite and the rider segment it serves in the chosen city, with a reason for the city - A north-star metric with a precise definition, and why it beats installs or raw trip counts - Funnel and reliability metrics specific to low-end phones and weak networks - Guardrails for cannibalization of the main app, marketplace health, safety and payments - How to separate trips Uber Lite created from trips that would have happened anyway ### Follow-up Questions - Uber Lite trips are rising, but most of the growth comes from riders who used to book on the main app. Is that success? - Rider cancellations are higher on Uber Lite than on the main app in your city. How would you investigate? - Leadership asks whether to keep investing in Uber Lite or fold its improvements into the main app. Which numbers would you bring?