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

Vanguard

What factors are contributing to the recent 20% increase in customer support calls related to Vanguard's mobile app?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis User Experience Design Financial Services Fintech Investment Management User Experience Fintech Root Cause Analysis Mobile Apps Customer Support
Product Management Root Cause Analysis Question: Investigating mobile app customer support increase for financial services

Introduction

The recent 20% increase in customer support calls related to Vanguard's mobile app signals a significant shift in user experience. This analysis will systematically identify, validate, and address the root cause while considering both immediate and long-term implications for Vanguard's product ecosystem.

I'll approach this issue by first clarifying key details, ruling out external factors, and then diving deep into product understanding, metric breakdown, and hypothesis formation. We'll then validate our findings and develop a comprehensive resolution plan.

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 this might be related to a recent app update. Has there been a major release in the last 30-60 days?

Why it matters: Recent updates often correlate with support spikes. Expected answer: Yes, there was an update. Impact on approach: If yes, we'll focus on changes in that update.

  • Considering user segments, I'm curious if this increase is uniform across all user types. Are we seeing a disproportionate increase from any particular user segment (e.g., new users, power users, specific age groups)?

Why it matters: Helps narrow down potential causes. Expected answer: Increase mainly from older users. Impact on approach: If segmented, we'll tailor our investigation to that group.

  • Thinking about the nature of support calls, I'm wondering about the most common issues reported. What are the top 3 reasons for these support calls?

Why it matters: Identifies specific problem areas. Expected answer: Login issues, transaction errors, and navigation problems. Impact on approach: Guides our focus to specific app functionalities.

  • Considering system performance, I'm curious if there have been any backend changes or server issues recently. Have we seen any unusual patterns in app performance metrics?

Why it matters: Rules out or confirms technical issues. Expected answer: No significant backend changes or performance issues. Impact on approach: If yes, we'll investigate technical root causes more deeply.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025