Introduction
The sudden 30% increase in customer support calls related to Judo Bank's online banking platform this month is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term and long-term implications for the platform and its users.
I'll approach this problem by first clarifying the context, then ruling out external factors before diving deep into the product's user journey, metric breakdown, and data analysis. From there, I'll form and validate hypotheses, conduct a root cause analysis, and propose a comprehensive resolution plan.
This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.
Step 1
Clarifying Questions (3 minutes)
Why it matters: Recent changes often correlate with support spikes. Expected answer: Yes, a new feature was rolled out. Impact on approach: If yes, we'd focus on the new feature's implementation and user experience.
Why it matters: Helps identify if the issue is widespread or localized. Expected answer: Calls are primarily from older users with savings accounts. Impact on approach: If segmented, we'd tailor our investigation to that specific user group.
Why it matters: Pinpoints specific areas of the platform causing issues. Expected answer: Login problems, transaction errors, and account balance discrepancies. Impact on approach: We'd prioritize investigating these specific functionalities.
Why it matters: Ensures the increase isn't due to a change in measurement. Expected answer: No changes to the logging system. Impact on approach: If no changes, we can rule out measurement errors and focus on actual platform issues.
Practice similar questions
Subscribe to access the full answer