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

Applied Systems

What factors are contributing to the recent 20% increase in customer support tickets related to Applied Systems's TAM agency management software?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Customer Empathy Insurance SaaS Agency Management User Experience Root Cause Analysis Customer Support Software Updates Insurance Tech
Product Management Root Cause Analysis Question: Investigating spike in support tickets for insurance agency software

Introduction

The recent 20% increase in customer support tickets related to Applied Systems's TAM agency management software is a concerning trend that requires immediate attention and a thorough root cause analysis. This issue not only impacts customer satisfaction but also has potential implications for the product's reputation and long-term success. In addressing this problem, I'll follow a systematic approach to identify, validate, and address the root cause while considering both immediate and long-term 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 product update. Has there been any significant changes or updates to the TAM software in the past 30-60 days?

Why it matters: Recent changes could directly correlate with the increase in support tickets. Expected answer: Yes, there was a major update to the user interface. Impact on approach: If confirmed, we'd focus on UI/UX issues and user adaptation.

  • Considering user segments, I'm wondering if this increase is uniform across all user types. Can you provide a breakdown of the ticket increase by user role or agency size?

Why it matters: This helps identify if the issue is more prevalent in specific user groups. Expected answer: The increase is more pronounced among smaller agencies. Impact on approach: We'd tailor our solution to address the needs of smaller agencies first.

  • Thinking about the nature of support tickets, are there any common themes or specific features mentioned more frequently in these tickets?

Why it matters: This helps pinpoint specific problematic areas within the software. Expected answer: Many tickets mention difficulties with the new reporting feature. Impact on approach: We'd prioritize investigating and improving the reporting functionality.

  • Considering external factors, has there been any change in the support ticket categorization or routing system in the last 3 months?

Why it matters: This could reveal if the increase is due to a change in how we're measuring or categorizing tickets. Expected answer: No changes to the ticketing system have been made. Impact on approach: We'd focus on product-related issues rather than measurement discrepancies.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025