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 .

What factors are contributing to the sudden 30% increase in customer complaints regarding Sumitomo Mitsui Banking's mobile banking app in the last two weeks?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Customer Experience Banking FinTech Mobile Applications User Experience Root Cause Analysis Mobile Banking App Performance Customer Complaints
Product Management Root Cause Analysis Question: Investigating sudden increase in mobile banking app complaints

Introduction

The sudden 30% increase in customer complaints regarding Sumitomo Mitsui Banking's mobile banking app over the past two weeks is a critical issue that demands immediate attention. To address this problem, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both short-term fixes and long-term implications for the product.

My analysis will follow a structured framework, beginning with clarifying questions to gather essential context, followed by a thorough examination of potential external factors. I'll then delve into the product's core functionality, break down the relevant metrics, and formulate data-driven hypotheses. Through rigorous root cause analysis and validation methods, we'll develop a comprehensive plan to address the issue and prevent future occurrences.

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 last month?

Why it matters: Recent changes could directly impact user experience and lead to increased complaints. Expected answer: Yes, there was an update two weeks ago. Impact on approach: If confirmed, we'd focus on changes introduced in the update.

  • Given the specificity of the 30% increase, I'm curious about our complaint tracking system. Has there been any change in how we categorize or record customer complaints recently?

Why it matters: Changes in complaint categorization could artificially inflate numbers. Expected answer: No changes in the complaint tracking system. Impact on approach: If unchanged, we'd focus on actual user experience issues rather than data anomalies.

  • Considering the broad nature of "complaints," I'm wondering about the specific types of issues users are reporting. What are the top three categories of complaints we're seeing?

Why it matters: Understanding the nature of complaints helps narrow down potential root causes. Expected answer: Login issues, transaction failures, and slow performance. Impact on approach: We'd prioritize investigating these specific areas of the app.

  • Given that banking apps often have different user segments, I'm thinking about demographic patterns. Are we seeing this increase across all user groups, or is it concentrated in specific segments?

Why it matters: Identifying affected segments could point to specific user needs or technical issues. Expected answer: The increase is primarily among users aged 50+. Impact on approach: We'd focus on usability and accessibility for older users.

  • Considering the critical nature of banking apps, I'm curious about any recent security measures implemented. Have there been any new security features or protocols added recently?

Why it matters: Enhanced security measures could potentially impact user experience. Expected answer: A new two-factor authentication system was implemented. Impact on approach: We'd investigate the implementation and user interaction with new security features.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025