Lyft product health monitoring: choosing and organizing the dashboard metrics

You are the product manager for Lyft. Describe the dashboard you would build to tell whether the app is healthy: what health means here, which metrics belong on it, how you would organize them, and how the dashboard would be used day to day. ```hint Start from one trip Trace a single trip from opening the app to being dropped off, and ask which number would move first if any step along the way broke. ``` ### Clarifying Questions - Does "the app" mean the rider app, the driver app, or Lyft's ride-hailing product as a whole? - Who reads the dashboard and how often: the product team every day, or leadership in a weekly review? - Is "health" about business performance, product and technical reliability, or both? - Should it cover every market and ride type, or a single city or service? ### What a Strong Answer Covers - A definition of health for Lyft, plus the dashboard's audience and how often it is read - A lead metric with the reason for choosing it, and the supporting metrics organized beneath it - How the chosen scope reflects the dependence between rider demand and driver supply - Quality, safety and reliability signals alongside growth and revenue - Segment cuts, alert thresholds, and how a team would act when a number moves ### Follow-up Questions - Completed rides drop sharply in one city over a single week. How would you use the dashboard to find the cause? - If leadership allowed only one number on the dashboard, which would you keep, and what could it hide? - How would the dashboard differ if you owned the driver app instead?