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

UST

How can we explain the sudden spike in customer support tickets related to UST's mobile payment app over the past week?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis User Experience Fintech Mobile Apps Customer Service Fintech Root Cause Analysis Customer Support Mobile Payments App Performance
Product Management Root Cause Analysis Question: Investigating sudden increase in mobile payment app support tickets

Introduction

The sudden spike in customer support tickets related to UST's mobile payment app over the past week is a critical issue that demands immediate attention and thorough analysis. As we delve into this problem, we'll employ a systematic approach to identify, validate, and address 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 app update. Has there been any significant changes or updates to the mobile payment app in the last 7-10 days?

Why it matters: Recent changes often correlate with sudden spikes in support tickets. Expected answer: Yes, there was an update released last week. Impact on approach: If confirmed, we'd focus on changes introduced in the update.

  • Considering user segments, I'm wondering if this is affecting all users equally. Are we seeing the spike across all user segments or is it concentrated in specific groups?

Why it matters: Helps narrow down potential causes and affected user base. Expected answer: The spike is more pronounced among iOS users. Impact on approach: We'd investigate iOS-specific issues or changes.

  • Given the nature of mobile payments, I'm curious about transaction volumes. Has there been any unusual activity or spikes in transaction volumes coinciding with the increase in support tickets?

Why it matters: Correlating with transaction data can reveal performance issues under load. Expected answer: Transaction volumes have remained stable. Impact on approach: We'd focus more on app functionality than backend processing.

  • Thinking about the support ticket content, I'm interested in the nature of the complaints. What are the top 3 issues being reported in these support tickets?

Why it matters: Identifies specific problem areas to investigate. Expected answer: Login issues, transaction failures, and app crashes are the most common. Impact on approach: We'd prioritize these areas in our root cause analysis.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025