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 .

What factors are contributing to the 20% increase in customer support calls related to Fidelity Investments's mobile app in the last quarter?

Prepared by NextSprints

12 mins
Report an error
Problem Solving Data Analysis User Experience Design Financial Services FinTech Investment Management User Experience Root Cause Analysis Mobile Apps Customer Support FinTech
Product Management Root Cause Analysis Question: Investigating increased customer support calls for a financial app

Introduction

The recent 20% increase in customer support calls related to Fidelity Investments's mobile app is a concerning trend that requires immediate attention. To address this issue, 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 recent app update. Has there been a major release or feature update in the last quarter?

Why it matters: Recent changes often correlate with support call spikes. Expected answer: Yes, a significant update was released. Impact on approach: If confirmed, we'd focus on new feature adoption and potential bugs.

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

Why it matters: Helps identify if the issue is universal or segment-specific. Expected answer: The increase is more pronounced among newer users. Impact on approach: We'd prioritize onboarding and new user experience improvements.

  • Regarding the nature of support calls, I'm wondering about the most common issues reported. What are the top three reasons customers are calling?

Why it matters: Pinpoints specific areas of the app causing friction. Expected answer: Login issues, transaction errors, and navigation confusion. Impact on approach: We'd focus on these specific areas for immediate improvements.

  • Thinking about external factors, has there been any significant market volatility or economic events that might drive increased app usage?

Why it matters: External events can impact user behavior and app interaction. Expected answer: Some market volatility, but not unusual for the period. Impact on approach: We'd consider how to better support users during high-stress periods.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025