How can Wealthsimple balance the simplicity of its robo-advisor service with offering more advanced customization options for experienced investors?

Introduction

Balancing simplicity with advanced customization in Wealthsimple's robo-advisor service presents a classic product trade-off. We need to maintain the ease of use that attracts novice investors while providing the depth of options that experienced users demand. This challenge touches on user experience, product strategy, and business model considerations.

I'll approach this analysis by examining the current product offering, identifying key stakeholders, and proposing a framework to evaluate potential solutions. We'll then design an experiment to test our hypotheses and outline a decision-making process for implementation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Wealthsimple is seeing increased churn among more sophisticated investors. Could you confirm if this is the case, and if so, what percentage of users are we losing to more customizable platforms?

Why it matters: Helps quantify the problem and justify potential changes Expected answer: Yes, losing 5-10% of high-value users annually Impact on approach: Would prioritize advanced features if churn is significant

• Business Context: Based on Wealthsimple's fee structure, I'm thinking the advanced customization might impact our revenue model. How do we currently monetize different user segments, and how might this change affect our margins?

Why it matters: Ensures solution aligns with business objectives Expected answer: Higher fees for advanced services, potential for increased AUM Impact on approach: Would focus on features that maintain or improve margins

• User Impact: I'm considering the different user personas we serve. Can you share insights on the distribution of novice vs. experienced investors in our user base, and their respective engagement levels?

Why it matters: Helps tailor solution to most impactful user segments Expected answer: 70% novice, 30% experienced; experienced users have 3x the AUM Impact on approach: Would inform balance between simplicity and advanced features

• Technical Feasibility: Thinking about our current architecture, how challenging would it be to implement modular advanced features without disrupting the core simple experience?

Why it matters: Determines feasibility and resource requirements Expected answer: Moderately challenging, requires 3-6 months of development Impact on approach: Would influence timeline and phasing of feature rollout

• Timeline: Given the competitive landscape, how urgent is this initiative? Are we looking at a near-term solution or a longer-term strategy?

Why it matters: Helps prioritize and scope the solution Expected answer: Medium urgency, aiming for implementation within 6-12 months Impact on approach: Would shape the depth and breadth of proposed changes