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

Onit

What factors are contributing to the increased average time-to-resolution for support tickets related to Onit's Enterprise Legal Management platform this month?

Prepared by NextSprints

12 mins
Report an error
Problem-Solving Data Analysis Strategic Thinking Legal Tech Enterprise Software Professional Services Root Cause Analysis Enterprise Software Product Troubleshooting Legal Tech Support Optimization
Product Management Root Cause Analysis Question: Investigating increased support ticket resolution time for legal management software

Introduction

The increased average time-to-resolution for support tickets related to Onit's Enterprise Legal Management platform this month is a critical issue that requires 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 strategic implications.

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 be a recent change in the platform. Has there been any significant update or feature release in the past month?

Why it matters: Recent changes often correlate with support issues. Expected answer: Yes, a major update was released. Impact on approach: If true, we'd focus on the new features and changes.

  • Considering user segments, I'm curious about the distribution of these increased resolution times. Are we seeing this across all customer types, or is it concentrated in specific segments?

Why it matters: Helps identify if the issue is universal or segment-specific. Expected answer: The issue is more prevalent in enterprise customers. Impact on approach: We'd tailor our solution to address enterprise-specific factors.

  • Thinking about the support process, has there been any change in the support team structure or ticketing system recently?

Why it matters: Internal changes can significantly impact resolution times. Expected answer: No major changes in the support structure. Impact on approach: We'd focus more on product-related issues rather than support processes.

  • Regarding the nature of tickets, are we seeing an increase in complexity of issues reported, or is it the same type of issues taking longer to resolve?

Why it matters: Helps distinguish between product complexity and support efficiency issues. Expected answer: The complexity of issues has increased. Impact on approach: We'd investigate why the product is generating more complex issues.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025