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 .

Why has Commonwealth Bank's NetBank mobile app seen a 15% drop in daily active users over the past month?

Prepared by NextSprints

12 mins
Report an error
Data Analysis Problem Solving User Experience Banking FinTech Mobile Apps User Retention Root Cause Analysis Mobile Banking FinTech App Analytics
Product Management Root Cause Analysis Question: Investigating mobile banking app user decline

Introduction

The Commonwealth Bank's NetBank mobile app has experienced a significant 15% drop in daily active users over the past month, raising concerns about user engagement and potential issues with the app's functionality or user experience. To address this problem, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both immediate and long-term implications for the product.

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 any major release or feature change in the last 1-2 months?

Why it matters: Recent changes often correlate with user behavior shifts. Expected answer: Yes, there was an update 6 weeks ago. Impact on approach: If confirmed, we'd focus on changes in that update.

  • Considering user segments, I'm curious about the distribution of the drop. Is the 15% decrease uniform across all user groups, or are certain segments more affected?

Why it matters: Helps identify if the issue is universal or specific to certain users. Expected answer: The drop is more pronounced among users aged 45+. Impact on approach: We'd investigate features or changes that might particularly impact older users.

  • Given the competitive landscape, I'm wondering about market factors. Have there been any significant changes or promotions from competing banking apps recently?

Why it matters: External factors could be drawing users away. Expected answer: No major competitor changes noted. Impact on approach: We'd focus more on internal factors if external influences are minimal.

  • Thinking about system reliability, I'm concerned about potential technical issues. Have there been any reported increases in app crashes, login failures, or slow performance in the past month?

Why it matters: Technical problems often lead to decreased usage. Expected answer: There's been a slight increase in reported login issues. Impact on approach: We'd prioritize investigating authentication and login processes.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025