Introduction
The unexpected 20% increase in customer support tickets related to Stori's mobile app functionality in the last two weeks is a critical issue that demands immediate attention. To address this problem, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both short-term fixes and long-term implications for our product strategy.
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 ticket increases. Expected answer: Yes, a minor update was released three weeks ago. Impact on approach: If confirmed, we'd focus on changes in that update.
Why it matters: Helps narrow down potential causes and affected users. Expected answer: The increase is primarily among newer users. Impact on approach: We'd investigate onboarding processes and new user experiences.
Why it matters: External events can drive unusual app usage patterns. Expected answer: No major market changes in the past month. Impact on approach: We'd focus more on internal factors if confirmed.
Why it matters: Helps identify if the issue is localized or systemic. Expected answer: Tickets are mainly about transaction history and balance discrepancies. Impact on approach: We'd prioritize investigating those specific features.
Why it matters: Ensures the increase isn't due to changes in measurement or categorization. Expected answer: No recent changes to the support ticket system. Impact on approach: Confirms the increase is real and not a measurement artifact.
Practice similar questions
Subscribe to access the full answer