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

NextSprints
NextSprints Icon NextSprints Logo
⌘K
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 .

What factors are contributing to the sudden 30% increase in customer support tickets related to Clarivate Analytics's Derwent Innovation patent database in the last two weeks?

Prepared by NextSprints

15 mins
Report an error
Problem-Solving Data Analysis Customer Experience Information Services Legal Tech Intellectual Property Data Analytics Root Cause Analysis Product Troubleshooting Customer Support Patent Database
Product Management Root Cause Analysis Question: Investigating sudden increase in support tickets for patent database

Introduction

The sudden 30% increase in customer support tickets related to Clarivate Analytics's Derwent Innovation patent database over the past two weeks is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term and long-term implications for the product and its users.

I'll approach this problem by first clarifying the context, then ruling out external factors before diving deep into the product's user journey, metric breakdown, and data analysis. From there, I'll form hypotheses, conduct root cause analysis, and propose validation methods and solutions.

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 product update. Has there been any significant change to the Derwent Innovation platform in the last month?

Why it matters: Recent changes often correlate with support ticket spikes. Expected answer: Yes, a new feature was rolled out three weeks ago. Impact on approach: If true, I'd focus on the new feature's implementation and user adoption.

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

Why it matters: Helps identify if the issue is universal or segment-specific. Expected answer: Tickets are primarily from enterprise users. Impact on approach: If true, I'd investigate enterprise-specific features or usage patterns.

  • Given the database nature of the product, I'm wondering about data integrity. Have there been any reported issues with data accuracy or completeness in the past month?

Why it matters: Data quality is crucial for a patent database. Expected answer: No significant data issues reported. Impact on approach: If false, I'd prioritize data integrity checks and potential data source problems.

  • Considering support processes, has there been any change in how support tickets are categorized or handled recently?

Why it matters: Changes in support processes could artificially inflate ticket numbers. Expected answer: No recent changes to support processes. Impact on approach: If false, I'd investigate the support system and ticket categorization methods.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025