Should ICICI Bank's mobile banking app prioritize adding new features or improving existing core functionality?

Introduction

The trade-off question at hand is whether ICICI Bank's mobile banking app should prioritize adding new features or improving existing core functionality. This scenario involves balancing innovation with user experience optimization in a competitive fintech landscape. I'll analyze this trade-off by examining the current product state, user needs, business objectives, and potential impacts of each approach.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming ICICI Bank is facing increased competition from fintech startups. Is this correct, and how has it impacted our market share recently?

Why it matters: Helps gauge the urgency of innovation vs. optimization Expected answer: Yes, with slight market share erosion Impact: Higher urgency might lean towards new features

• Business Context: Based on our current revenue model, I'm thinking core functionality might be driving most transactions. Could you share how our revenue is split between basic banking services and value-added features?

Why it matters: Aligns solution with primary revenue streams Expected answer: 70% from core services, 30% from additional features Impact: Higher core revenue would prioritize improving existing functionality

• User Impact: Considering user segments, I'm guessing we have a mix of tech-savvy and traditional users. Can you provide a breakdown of our user demographics and their feature usage patterns?

Why it matters: Ensures solution caters to key user segments Expected answer: 60% traditional users, 40% tech-savvy, with varying feature adoption Impact: Higher traditional user base might favor core functionality improvements

• Technical: Given the complexity of banking systems, I'm assuming there might be technical debt affecting our ability to add new features quickly. What's our current technical architecture's flexibility for feature additions?

Why it matters: Assesses feasibility and resource requirements Expected answer: Moderate flexibility, some legacy systems Impact: Lower flexibility might favor improving existing features first

• Resource: Thinking about our development capacity, I'm curious about our current team structure. How are our engineering and product teams allocated between maintenance and new feature development?

Why it matters: Determines resource availability for each approach Expected answer: 60% maintenance, 40% new development Impact: Higher maintenance allocation might favor improving core functionality