Introduction
The sudden 30% increase in support tickets related to Savvas Learning's MyPerspectives ELA curriculum last week 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 product and its users.
I'll approach this problem by first clarifying key details, ruling out external factors, and then diving deep into the product's user journey and metrics. From there, I'll form data-driven hypotheses, conduct root cause analysis, and propose validation methods and solutions.
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 spikes. Expected answer: Yes, a new feature was rolled out two weeks ago. Impact on approach: If confirmed, I'd focus on that feature in my analysis.
Why it matters: Identifying affected segments helps narrow down potential causes. Expected answer: Majority of tickets are from teachers. Impact on approach: I'd prioritize investigating teacher-specific features and workflows.
Why it matters: Usage patterns can significantly impact support ticket volume. Expected answer: Yes, many schools started a new term recently. Impact on approach: I'd consider how increased usage might expose existing issues.
Why it matters: Changes in support processes can artificially inflate ticket numbers. Expected answer: No changes to the support system. Impact on approach: If confirmed, I'd focus on product-related issues rather than support system changes.
Practice similar questions
Subscribe to access the full answer