Metrics question

If you were the PM for Lyft, what dashboard would you build to track the health of the app?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests dashboard design: picking the right set of health metrics across the two sides of a marketplace, not just app crash rates.

Clarify who reads this dashboard, an exec needing a daily pulse versus an on-call engineer, since that changes granularity.
Group metrics by the two-sided marketplace: rider side (requests, wait time, cancellation rate, price surge frequency) and driver side (acceptance rate, idle time, earnings per hour).
Add a marketplace-balance metric, like requests-to-available-drivers ratio by region, since imbalance is the core Lyft risk.
Add reliability metrics: app crash rate, ETA accuracy, and payment failure rate, since these erode trust fast.
Rank the top-line metric for the header: completed-ride rate (requests that end in a successful trip), since it summarizes both sides at once.

Organizes the dashboard by rider, driver, and marketplace-balance sections instead of a flat list, showing structured thinking.
Picks completed-ride rate as the single top metric because it fails only when either side of the marketplace breaks down.
Includes a regional cut, since Lyft's health varies city to city and an aggregate number can hide local supply crises.
Adds a leading indicator, surge frequency and duration, that flags supply problems before cancellation rate visibly spikes.

Listing only rider-facing metrics and ignoring driver supply health, which is just as critical to the marketplace.
Building a flat, unprioritized list instead of naming which single metric matters most at a glance.

Chapters of the AI PM course that teach what this question tests.