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

LexisNexis

What factors are contributing to the 30% increase in customer support tickets related to LexisNexis's PatentSight tool in Q2?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis User Experience Design Legal Tech Intellectual Property SaaS User Experience Root Cause Analysis Customer Support Data Accuracy Patent Analytics
Product Management Root Cause Analysis Question: Investigating increased support tickets for LexisNexis PatentSight tool

Introduction

The 30% increase in customer support tickets for LexisNexis's PatentSight tool in Q2 is a significant 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 seasonal component. Has this increase been observed in previous Q2 periods?

Why it matters: Helps distinguish between cyclical patterns and unique issues. Expected answer: No similar increase in previous Q2 periods. Impact on approach: If seasonal, we'd focus on capacity planning; if not, we'd investigate recent changes.

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

Why it matters: Identifies whether the issue is widespread or localized to certain user groups. Expected answer: Increase is primarily seen in enterprise users. Impact on approach: If concentrated, we'd focus on that segment's specific needs or recent changes affecting them.

  • Thinking about recent changes, have there been any significant updates to PatentSight in the last 3-6 months?

Why it matters: Helps correlate the increase with potential product or system changes. Expected answer: A major UI overhaul was implemented 2 months ago. Impact on approach: If recent changes exist, we'd scrutinize their impact on user experience and functionality.

  • Regarding ticket categories, I'm wondering if there's a pattern in the types of issues being reported. Are certain categories of tickets showing a disproportionate increase?

Why it matters: Pinpoints specific areas of the product or user experience that may be problematic. Expected answer: A significant increase in "data accuracy" related tickets. Impact on approach: We'd focus our investigation on the specific areas showing the most substantial increase.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025