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 .

Company focus

Netcompany

What caused the sudden spike in customer support tickets related to Netcompany's mobile banking app last week?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Technical Understanding Fintech Banking Mobile Apps Root Cause Analysis Product Quality Bug Fixing Mobile Banking Customer Support
Product Management Root Cause Analysis Question: Investigating mobile banking app support ticket surge

Introduction

The sudden spike in customer support tickets related to Netcompany's mobile banking app last week is a critical issue that demands immediate attention and thorough analysis. As we delve into this problem, we'll follow a systematic approach to identify, validate, and address the root cause while considering both short-term fixes and long-term implications for our product strategy.

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 app update. Has there been any significant changes or updates to the mobile banking app in the past week or two?

Why it matters: Recent updates often correlate with 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 issue is affecting all users equally. Are we seeing a disproportionate number of tickets from a specific user group, such as iOS vs. Android users, or perhaps users of certain device models?

Why it matters: Helps narrow down potential technical or compatibility issues. Expected answer: The majority of tickets are coming from iOS users. Impact on approach: We'd prioritize investigating iOS-specific issues.

  • Given the nature of banking apps, I'm curious about the types of issues being reported. Are the support tickets clustered around specific functionalities, like login problems, transaction failures, or balance discrepancies?

Why it matters: Identifies the most impacted features and potential security concerns. Expected answer: Most tickets relate to failed transactions and balance update delays. Impact on approach: We'd focus on the transaction processing and balance update systems.

  • Considering potential external factors, have there been any significant changes in the banking sector or regulatory environment that might have impacted our app's functionality?

Why it matters: External factors can sometimes trigger internal issues or user confusion. Expected answer: No major external changes have been reported. Impact on approach: We'd focus more on internal factors and recent product changes.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Nov 19, 2024