Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

Oyster

What caused the sudden 30% increase in support tickets related to Oyster's contractor management platform last week?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis User Experience HR Tech SaaS Global Employment User Experience Data Analysis Root Cause Analysis Support Optimization Contractor Management
Product Management Root Cause Analysis Question: Investigating sudden increase in support tickets for contractor management platform

Introduction

The sudden 30% increase in support tickets related to Oyster's contractor management platform last week is a critical issue that demands immediate attention. As we dive into this analysis, we'll systematically identify potential root causes, validate our hypotheses, and develop a comprehensive plan to address the problem. Our approach will balance short-term fixes with long-term strategic improvements to enhance the platform's performance and user satisfaction.

Framework overview

This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.

Step 1

Clarifying Questions (3 minutes)

  • Looking at the timing, I'm thinking there might have been a recent platform update. Has there been any significant change or feature release in the past two weeks?

Why it matters: Recent changes often correlate with support ticket spikes. Expected answer: Yes, a new feature was released. Impact on approach: If true, we'd focus on the new feature's implementation and user onboarding.

  • Considering user segments, I'm curious about the distribution of these tickets. Are they coming from a specific type of user or spread across all user types?

Why it matters: Helps identify if the issue is isolated to a particular user group. Expected answer: Tickets are primarily from new users. Impact on approach: If true, we'd examine the onboarding process and new user experience.

  • Thinking about the nature of the tickets, I'm wondering about the most common issues reported. What are the top three categories of problems users are reporting?

Why it matters: Identifies patterns in the reported issues. Expected answer: Login issues, data syncing problems, and UI navigation confusion. Impact on approach: Would guide our technical investigation and UX review.

  • Considering external factors, has there been any change in the regulatory landscape for contractor management that might have impacted our users?

Why it matters: External factors can drive sudden changes in platform usage or requirements. Expected answer: No significant regulatory changes. Impact on approach: If true, we'd focus more on internal factors and platform changes.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025