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

ConnectWise

Why has the average resolution time for tickets in ConnectWise Manage increased by 35% for enterprise customers in the last two weeks?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem Solving Technical Understanding IT Services SaaS Managed Service Providers Performance Optimization Root Cause Analysis Enterprise Software Customer Support Ticketing Systems
Product Management Root Cause Analysis Question: Investigating ConnectWise Manage's increased ticket resolution time for enterprise customers

Introduction

The recent 35% increase in average resolution time for enterprise customer tickets in ConnectWise Manage is a critical issue that demands immediate attention. This significant shift in a key performance metric could have far-reaching implications for customer satisfaction, operational efficiency, and ultimately, the company's bottom line. 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 have been a recent system update. Has there been any significant changes to ConnectWise Manage in the last month?

Why it matters: System changes often impact performance metrics. Expected answer: Yes, there was a major update two weeks ago. Impact on approach: If confirmed, we'd focus on post-update issues.

  • Considering the specificity to enterprise customers, I'm wondering about their unique needs. Are enterprise tickets typically more complex than other customer segments?

Why it matters: Complexity could explain longer resolution times. Expected answer: Yes, enterprise tickets often involve more intricate issues. Impact on approach: We'd investigate if recent changes have disproportionately affected complex ticket handling.

  • Given the magnitude of the increase, I'm curious about ticket volume. Has there been a significant spike in the number of tickets from enterprise customers recently?

Why it matters: Volume changes could strain resources and increase resolution times. Expected answer: Ticket volume has remained relatively stable. Impact on approach: If volume isn't the issue, we'd focus more on internal processes or system performance.

  • Thinking about potential data anomalies, I'm wondering about the ticket categorization process. Has there been any recent change in how tickets are classified or prioritized?

Why it matters: Changes in classification could artificially inflate resolution times. Expected answer: No recent changes to ticket categorization. Impact on approach: If confirmed, we'd rule out data classification issues and focus on actual resolution processes.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025