Should NatWest prioritize expanding its mobile banking app features or improving the stability and speed of existing core functions?

Introduction

The trade-off between expanding mobile banking app features and improving existing core functions is a critical decision for NatWest. This scenario touches on the heart of product strategy: balancing innovation with stability. I'll analyze this trade-off by examining user needs, business objectives, and technical considerations to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming NatWest's mobile app is a key touchpoint for customers. Could you share any recent customer feedback or satisfaction scores for the app?

Why it matters: Helps prioritize user pain points vs. desired new features Expected answer: Mixed feedback, with some stability issues reported Impact: Would lean towards improving core functions if satisfaction is low

• Business Context: Based on industry trends, I imagine digital engagement is a key metric. How does mobile app usage tie into NatWest's broader digital transformation strategy?

Why it matters: Aligns solution with strategic business objectives Expected answer: Critical for reducing branch costs and increasing digital revenue Impact: Might favor new features if they drive significant engagement increases

• User Impact: I'm thinking about different user segments. Can you tell me about the app usage patterns across various customer demographics?

Why it matters: Ensures solution addresses needs of key user groups Expected answer: Higher usage among younger customers, but growing adoption in older segments Impact: Could influence feature prioritization based on target growth segments

• Technical: Considering the complexity of banking systems, what's the current architecture of the app and its backend integrations?

Why it matters: Assesses feasibility and potential challenges of both options Expected answer: Monolithic core with some microservices for newer features Impact: Might favor stability improvements if architecture is limiting new feature development

• Resource: I'm curious about the team structure. How are the mobile app development and maintenance teams currently organized?

Why it matters: Determines capacity for parallel work on stability and new features Expected answer: Separate teams for core maintenance and new feature development Impact: Could influence ability to pursue both paths simultaneously