Should Betterment prioritize adding more advanced investment features or simplifying the user interface for broader appeal?

Introduction

The trade-off between adding advanced investment features and simplifying the user interface for Betterment is a critical decision that could significantly impact the platform's growth and user satisfaction. This scenario touches on the classic product management challenge of balancing complexity with accessibility. I'll analyze this trade-off by examining the product context, potential impacts, and data-driven decision-making processes.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking Betterment's current user base might be split between novice and experienced investors. Could you share the breakdown of our user segments and their engagement levels?

Why it matters: Helps tailor features to user needs and preferences Expected answer: 60% novice, 40% experienced; experienced users more engaged Impact: Would influence whether to prioritize advanced features or simplification

• Business Context: Based on our revenue model, I assume we earn from assets under management. Is this correct, and are there any other significant revenue streams?

Why it matters: Aligns product decisions with revenue generation Expected answer: Primarily AUM-based, with some subscription revenue Impact: Would affect the balance between attracting new users and retaining high-value clients

• User Impact: I'm curious about our user retention rates. Do we see higher churn among novice users or those with larger portfolios?

Why it matters: Identifies pain points and opportunities for improvement Expected answer: Higher churn among novice users in the first 3 months Impact: Might lean towards UI simplification if novice retention is a priority

• Technical: Regarding our current tech stack, how modular is our architecture? Could we implement advanced features without disrupting the core experience?

Why it matters: Assesses feasibility and potential development challenges Expected answer: Moderately modular, some refactoring needed for major changes Impact: Influences timeline and resource allocation for either option

• Resource: What's our current product and engineering team capacity? Are we staffed to handle both UI overhauls and complex feature development?

Why it matters: Determines realistic scope and timeline for changes Expected answer: Teams at 80% capacity, hiring in progress Impact: Might necessitate phased approach or prioritization based on team strengths