Should Acorns prioritize expanding its investment portfolio options or focus on simplifying the user interface for easier onboarding?

Introduction

The trade-off between expanding Acorns' investment portfolio options and simplifying the user interface for easier onboarding presents a critical decision point for the company's growth strategy. This scenario touches on the core tension between product depth and user accessibility, a common challenge in fintech. I'll analyze this trade-off by examining key business factors, user impact, technical considerations, and potential outcomes to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Business Context: I'm thinking Acorns' primary revenue model is based on subscription fees and assets under management. Could you confirm if this is correct and if there are any other significant revenue streams?

Why it matters: Helps prioritize features that directly impact revenue growth Expected answer: Confirmation of revenue model, possibly including payment for premium features Impact on approach: Would influence whether to focus on user acquisition or increasing investment amounts

• User Impact: Based on current user behavior, I'm assuming a significant portion of users are new to investing. Is this accurate, and do we have data on the percentage of users who actively manage their portfolios versus those who set and forget?

Why it matters: Determines the balance between simplicity and advanced features Expected answer: Majority of users are novice investors with a small percentage of active traders Impact on approach: Would guide the level of complexity in new portfolio options

• Technical Feasibility: Considering the existing architecture, I'm guessing adding new investment options might be less complex than a major UI overhaul. Is this a fair assumption?

Why it matters: Affects implementation timeline and resource allocation Expected answer: Confirmation of relative complexity of each option Impact on approach: Would influence the phasing of feature rollouts

• Resource Allocation: Given the trade-off, I'm thinking this might involve reallocating resources from one team to another. Do we have flexibility in our current team structure to shift focus?

Why it matters: Determines the feasibility of pursuing either option aggressively Expected answer: Some flexibility exists, but with potential impact on ongoing projects Impact on approach: Would inform the scale and speed of implementation

• Timeline Pressure: I'm assuming there's some urgency to make this decision, perhaps due to market conditions or competitive pressure. Can you share any specific timeline constraints we're working with?

Why it matters: Helps prioritize short-term gains vs. long-term strategy Expected answer: Decision needed within next quarter to inform annual planning Impact on approach: Would influence whether to recommend a phased approach or all-in strategy