Should DBS Bank prioritize expanding its digibank mobile app features or focus on improving the stability of existing core banking functions?

Introduction

The trade-off between expanding DBS Bank's digibank mobile app features and improving the stability of existing core banking functions presents a critical strategic decision. This scenario encapsulates the classic product management challenge of innovation versus stability. I'll analyze this trade-off by examining the business context, user impact, technical considerations, and strategic implications to provide a comprehensive recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking digital banking adoption might be accelerating. Could you share any data on our digibank app's user growth rate over the past year?

Why it matters: Helps gauge market demand and potential impact of new features Expected answer: 20-30% year-over-year growth Impact on approach: High growth would favor feature expansion, low growth might prioritize stability

• Considering our revenue model, I'm assuming transaction fees are a significant income source. What percentage of our revenue comes from digital transactions versus traditional banking services?

Why it matters: Indicates the financial impact of digital banking on our bottom line Expected answer: 40-50% from digital transactions Impact on approach: Higher digital revenue would justify more investment in the app

• Looking at user behavior, I'm curious about our app's current stability. What's our average app crash rate, and how does it compare to industry standards?

Why it matters: Helps quantify the urgency of stability improvements Expected answer: 1-2% crash rate, slightly above industry average Impact on approach: Higher crash rates would shift focus towards stability

• Regarding our technical infrastructure, I'm wondering about our current system's scalability. How close are we to reaching our maximum capacity for handling concurrent users?

Why it matters: Indicates whether stability issues are tied to scalability limitations Expected answer: Operating at 70-80% of maximum capacity Impact on approach: Near-capacity operation would prioritize infrastructure improvements

• Considering our development resources, what's the current split of our engineering team between feature development and stability/maintenance work?

Why it matters: Helps understand our current resource allocation and capacity for change Expected answer: 60% feature development, 40% stability/maintenance Impact on approach: Heavily skewed allocation might indicate a need for rebalancing