How should ANZ balance increasing mobile app features versus maintaining simplicity in its GoMoney app?

Introduction

Balancing the addition of new features in ANZ's GoMoney mobile app while maintaining its simplicity is a critical product trade-off. This scenario involves weighing the benefits of enhanced functionality against the potential drawbacks of increased complexity. 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)

• Based on recent market trends, I'm thinking user expectations for mobile banking features have evolved rapidly. Could you share any recent user research or feedback indicating specific feature requests or pain points with the current GoMoney app?

Why it matters: Helps prioritize features based on actual user needs Expected answer: Several highly requested features, some usability concerns Impact on approach: Would focus on balancing most-requested features with usability improvements

• Considering ANZ's strategic priorities, I'm assuming digital transformation and customer retention are key focus areas. How does enhancing the GoMoney app align with ANZ's overall business strategy and revenue goals?

Why it matters: Ensures alignment between product decisions and business objectives Expected answer: High priority, critical for customer engagement and digital banking adoption Impact on approach: Would justify more resources for app development and user experience design

• Looking at the technical architecture, I'm wondering about the app's current performance and scalability. What are the technical constraints or opportunities we should be aware of when considering new features?

Why it matters: Helps assess feasibility and potential technical debt Expected answer: Some legacy systems, but recent investments in modernizing infrastructure Impact on approach: Would influence feature prioritization and implementation strategy

• Regarding resource allocation, I'm curious about the current team structure and capacity. What resources (design, development, QA) are available for this initiative, and are there any budget constraints we should consider?

Why it matters: Determines the scope and timeline of potential changes Expected answer: Dedicated mobile team with some flexibility in resources Impact on approach: Would help in planning feature rollout and determining the pace of changes

• Considering market dynamics, I'm thinking about competitive pressures. What's the timeline we're working with, and are there any specific milestones or market events driving urgency for these changes?

Why it matters: Helps balance short-term needs with long-term product vision Expected answer: Aim to release major updates within 6 months to stay competitive Impact on approach: Would influence the prioritization of features and the phasing of implementation