Metrics question
You are the product manager for Lyft Direct Debit Card for drivers. The product just launched. How do you build this product's first dashboard?
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests dashboard design for a brand-new product: choosing the first handful of metrics that show whether the launch is healthy, not a fully mature reporting suite.
How to approach it
- Clarify the product's goal: the Direct Debit Card helps drivers access earnings instantly, so the dashboard should track adoption and usage of that core value.
- Propose adoption metrics: cards activated as a percentage of eligible drivers, and time from eligibility to activation.
- Propose usage metrics: transactions per active cardholder per week, and average balance held (a sign drivers trust and rely on the card).
- Propose a guardrail metric: failed transaction rate and support ticket volume related to the card, since early product issues need fast visibility.
- Propose a business metric: interchange revenue or cost savings versus drivers cashing out through slower, more expensive methods.
- Keep the first version of the dashboard to 5 to 7 metrics maximum, since a brand-new product does not need a sprawling report yet.
What a strong answer includes
- Focuses the first dashboard on activation and usage, the two things that prove product-market fit for a just-launched financial product, rather than a broad metrics dump.
- Includes a trust signal, average balance held, since drivers keeping money on the card indicates real confidence in it.
- Adds a guardrail, failed transactions and support tickets, since financial products need fast error visibility from day one.
- Deliberately keeps the first dashboard small (5 to 7 metrics), which is the right instinct for a just-launched product with limited historical data.
Common mistakes
- Building an overly comprehensive dashboard with dozens of metrics before there is enough data or need for that.
- Omitting a guardrail for transaction failures, which matters enormously for a financial product's trust.
Likely follow-up questions
- Which single metric would you check first every morning after launch?
- How would you evolve this dashboard as the product matures past the first few months?
More metrics questions
- Late deliveries lead to customer churn. What data we should look at to prove this hypothesis for a food delivery app?PayPal · Metrics · Medium
- How would reduce cancellations for Uber?Shopify · Metrics · Medium
- There is a data point that indicates that there are more Uber drop-offs at the airport than pick-ups from the airport. Why is this the case and what would you do within the product to change that?PayPal · Metrics · Hard
- How would you measure the success of Uber Ride?Lyft · Metrics · Easy
- If a large number of drivers are dropping out of a particular city, why would it be?Lyft · Metrics · Medium
- Drivers are dropping out of a city on Lyft. How do you figure out what's going on?PayPal · Metrics · Medium
More questions from these companies
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 2: Data fluency: SQL, logs, and reading the truth yourself
- Chapter 14: Get the job: the AI PM interview loop