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

BBVA

What factors are causing the sudden 30% increase in customer service calls related to BBVA's online bill pay feature this quarter?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem-Solving User Experience Design Banking Financial Services Technology User Experience Product Metrics Root Cause Analysis Customer Service FinTech
Product Management Root Cause Analysis Question: Investigating sudden increase in customer service calls for online bill pay feature

Introduction

The sudden 30% increase in customer service calls related to BBVA's online bill pay feature this quarter is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term fixes and long-term strategic implications.

To tackle this problem, I'll follow a structured approach:

  1. Clarify the situation
  2. Rule out external factors
  3. Understand the product and user journey
  4. Break down the metric
  5. Gather and prioritize data
  6. Form hypotheses
  7. Conduct root cause analysis
  8. Validate findings and propose next steps
  9. Present a decision framework
  10. Outline a 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 there might be a recent change in the bill pay system. Has there been any significant update or feature release in the past quarter?

Why it matters: Recent changes often correlate with spikes in customer service calls. Expected answer: Yes, there was a UI update two weeks ago. Impact on approach: If confirmed, we'd focus on the UI change as a primary factor.

  • Considering user segments, I'm curious about the distribution of these calls. Are they coming predominantly from a specific user group, such as new users or long-time customers?

Why it matters: This helps identify if the issue is widespread or localized to a particular segment. Expected answer: The increase is seen across all user segments. Impact on approach: A widespread issue would suggest a systemic problem rather than a segment-specific one.

  • Regarding the nature of these calls, I'm wondering about the specific issues being reported. What are the top 3 reasons customers are calling about the bill pay feature?

Why it matters: Understanding the nature of complaints helps narrow down potential root causes. Expected answer: Difficulty in setting up new payees, payment failures, and confusion about new UI elements. Impact on approach: This would guide our focus on specific areas of the bill pay process for investigation.

  • Thinking about system performance, has there been any change in server response times or error rates for the bill pay feature in this period?

Why it matters: Technical issues often manifest as increased customer service calls. Expected answer: There's been a 15% increase in server response time during peak hours. Impact on approach: This would shift our focus to backend performance issues as a potential root cause.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025