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

DBS digibank

Why has DBS digibanc's mobile app login success rate dropped by 15% over the past week?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Technical Understanding Banking Fintech Mobile Apps User Experience Performance Optimization Root Cause Analysis Authentication Mobile Banking
Product Management Root Cause Analysis Question: Investigating sudden drop in mobile banking app login success rate

Introduction

The recent 15% drop in DBS digibank's mobile app login success rate over the past week is a critical issue that demands immediate attention. This significant decline in a core functionality metric could have far-reaching consequences for user experience, customer retention, and overall business performance. 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 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)

  • Given the sudden drop, I'm wondering about recent changes. Have there been any updates to the app or backend systems in the past 10 days?

Why it matters: Recent changes often correlate with performance issues. Expected answer: Yes, a minor update was pushed last week. Impact on approach: If confirmed, I'd focus on regression testing and rollback options.

  • Considering user segments, is this drop uniform across all user types or more pronounced in specific groups?

Why it matters: Helps narrow down potential causes and affected user base. Expected answer: The drop is more significant among Android users. Impact on approach: I'd prioritize Android-specific investigations if this is the case.

  • Looking at the timing, I'm curious about any unusual traffic patterns. Has there been any significant change in login attempts or overall app usage?

Why it matters: Unusual traffic could indicate external factors or potential security issues. Expected answer: Login attempts have remained stable, but successful logins have decreased. Impact on approach: This would suggest focusing on the login process itself rather than external factors.

  • Regarding system health, have there been any reported issues with authentication servers or related infrastructure?

Why it matters: Backend issues could explain widespread login problems. Expected answer: No major outages reported, but some intermittent slowdowns noted. Impact on approach: I'd investigate potential capacity or configuration issues if slowdowns are confirmed.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 8, 2025