← All questions
Product sensestretch
You designed a feature for ride-sharing drivers. How would you know a month after launch whether it worked?
How to approach it
Tie the measure back to the problem the feature solved for drivers. Then add a guardrail so you notice if riders or the business pay for it.
How a strong answer opens
“First I'd restate the driver problem the feature was built to solve, because the main metric should come straight from it. Then I'll add guardrails for riders and the business.”
Outline of a strong answer
Try answering out loud for a few minutes before you open this.
- Restate the driver problem the feature targets
- Pick a primary metric tied to it, such as idle time per hour
- Add adoption and repeat use metrics
- Add guardrails for rider wait time and cancellations
- Compare against a holdout group or a clean before-and-after
- Say what result would make you roll back
Where this question usually goes wrong
Reporting adoption alone, or a loose before-and-after comparison, without a holdout group or guardrails on rider wait time and cancellations.
Learn the method
Close with how you would measure it in Module 1, Product sense and design.
The full kit has worked answers in full, start to finish, for every round type. $129 once.
More product sense questions
- Design a voting experience for a city election.
- Design a product for dog owners.
- What is your favorite product, and why?
- Tell me about a product you use every day that you think is badly designed. How would you fix it?
- Pick an app on your phone you love. How would you improve it for someone opening it for the first time?