Introduction
The sudden 30% increase in support tickets related to Procore Technologies's Bid Management feature 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 our product and users.
I'll approach this problem by first clarifying the context, then ruling out external factors before diving deep into the product ecosystem, metric breakdown, and data analysis. From there, I'll form 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 minor UI update was released. Impact on approach: If yes, I'd focus on the update's impact; if no, I'd look at other factors.
Why it matters: Helps identify if it's a targeted issue or a system-wide problem. Expected answer: Mostly from new users in the construction industry. Impact on approach: If specific, I'd focus on that segment; if general, I'd look at broader system issues.
Why it matters: Identifies the specific problems users are facing. Expected answer: Difficulty in bid submission, error messages, slow loading times. Impact on approach: Would guide my technical investigation and hypothesis formation.
Why it matters: Ensures we're comparing apples to apples in our data. Expected answer: No changes in ticket categorization or counting methods. Impact on approach: If changed, I'd reassess the 30% increase; if not, I'd proceed with current data.
Practice similar questions
Subscribe to access the full answer