Should Intuit prioritize adding new features to QuickBooks to attract larger businesses, or focus on simplifying the interface for small business owners?

Introduction

The trade-off we're examining today is whether Intuit should prioritize adding new features to QuickBooks to attract larger businesses or focus on simplifying the interface for small business owners. This scenario touches on the classic product management challenge of balancing feature expansion with user experience simplification.

To address this, I'll analyze the current product landscape, identify key metrics, design an experiment, and provide a data-driven recommendation. My approach will consider both short-term gains and long-term strategic implications for QuickBooks and Intuit as a whole.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking larger businesses might represent a significant growth opportunity. Could you share how our current revenue is split between small and large business customers?

Why it matters: Helps quantify the potential impact of targeting larger businesses Expected answer: 80% from small businesses, 20% from larger ones Impact on approach: A higher percentage from larger businesses might justify more investment in advanced features

• Considering our product roadmap, I'm assuming we have upcoming releases planned. How does this decision align with our current development cycle and resource allocation?

Why it matters: Ensures the recommendation fits within existing constraints Expected answer: Next major release in 6 months, resources currently split 70/30 between maintenance and new features Impact on approach: A near-term release might favor quick wins in simplification

• Looking at user behavior, I'm curious about our churn rates. Are we seeing higher churn among small businesses or larger enterprises?

Why it matters: Identifies which segment might need more immediate attention Expected answer: Higher churn among small businesses Impact on approach: Would prioritize simplification to retain the core small business user base

• From a technical standpoint, I'm wondering about the complexity of our current codebase. How modular is our architecture, and how easily can we add new features without disrupting the existing user experience?

Why it matters: Assesses the feasibility and potential risks of adding new features Expected answer: Moderately modular, but some legacy code creates challenges Impact on approach: Might favor a phased approach to feature addition, coupled with gradual interface improvements