Should Monzo prioritize developing new features or improving existing ones?

Introduction

The trade-off between developing new features and improving existing ones is a critical decision for Monzo's product strategy. This scenario involves balancing innovation with optimization, considering user needs, technical constraints, and business goals. I'll analyze this trade-off by examining the product context, identifying key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Monzo's current market position and growth stage. Could you provide more context on where Monzo stands in terms of user acquisition and retention?

Why it matters: Helps determine if we should focus on attracting new users or improving experience for existing ones. Expected answer: Steady growth, but facing increased competition. Impact on approach: Would influence whether to prioritize new features for acquisition or improvements for retention.

• Business Context: Based on fintech trends, I'm assuming Monzo is exploring new revenue streams. How does this trade-off align with our current revenue model and strategic priorities?

Why it matters: Ensures alignment between product decisions and business objectives. Expected answer: Exploring additional financial products and services. Impact on approach: Would guide feature development towards areas with highest revenue potential.

• User Impact: Considering the diverse user base, I'm curious about which user segments are most affected by this decision. Can you share insights on user feedback or pain points?

Why it matters: Helps prioritize improvements or new features based on user needs. Expected answer: Core banking users satisfied, but power users seeking advanced features. Impact on approach: Would influence whether to focus on core improvements or innovative new features.

• Technical: Given the complexity of financial systems, I'm wondering about our technical capacity. What are our current technical constraints or opportunities that might impact this decision?

Why it matters: Ensures feasibility and efficiency of development efforts. Expected answer: Robust core banking infrastructure, but limited resources for new integrations. Impact on approach: Would affect the balance between improving existing systems and developing new capabilities.

• Resource Allocation: Considering team capacity, I'm thinking about how our current resources are allocated. Can you provide an overview of our team structure and any resource constraints?

Why it matters: Helps determine realistic scope for development efforts. Expected answer: Balanced team, but stretched thin across multiple projects. Impact on approach: Would influence whether to focus efforts on fewer, high-impact initiatives or spread across multiple areas.