App store ratings for Grab dropped from 4.4 to 3.9 over the past month.
How do you diagnose the cause?
About this question
Category
Product Execution
Subcategory
Root Cause Analysis
Difficulty
Easy
Est. time
30 min
What this question helps you practice
This product execution question tests how you diagnose a sudden quality or perception problem. A strong response should separate symptoms from root causes, segment the rating drop, inspect recent changes, and propose a focused investigation plan before jumping to fixes.
How to practice
Clarify the metric drop
Define rating source, time window, affected platforms, geography, app version, and user segments.
Form hypotheses
Check recent releases, outages, pricing or policy changes, driver/rider experience issues, and competitor events.
Prioritize investigation and response
Rank hypotheses by impact and confidence, then propose immediate mitigations and monitoring.
Strong answer signals
Segments the drop by app version, OS, geography, user type, and review theme.
Separates correlation from likely causation and names data needed to validate each hypothesis.
Balances quick user-facing mitigation with a deeper root-cause investigation.
Common mistakes
Jumping straight to a feature fix without diagnosing the affected segment.
Looking only at average rating and ignoring review volume, cohort, and version changes.
Treating app store ratings as the only signal of product quality.
Ready to try it?
Practice your answer in the interactive workspace.
Keep practicing
Explore frameworks and related prompts that build the same interview muscle.
Recommended frameworks
5 Whys Analysis: Uncovering Root Causes in Product Execution
Discover the 5 Whys technique—a powerful framework that helps Product Managers peel back the layers of symptoms to pinpoint the exact failure points in a system. More than just repeating "Why," it is the art of causal inquiry to prevent recurring issues.
