How can Fidelity Investments balance the simplicity of its Fidelity Go robo-advisor platform with the need for more advanced features requested by experienced investors?

Introduction

Balancing simplicity and advanced features in Fidelity Go's robo-advisor platform presents a critical product trade-off. We need to maintain the ease of use that attracts new investors while satisfying the demands of experienced users seeking more sophisticated tools. I'll analyze this challenge through the lens of user segmentation, feature prioritization, and platform scalability.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market positioning of Fidelity Go. Could you share how Fidelity Go currently compares to competitors in terms of user base and feature set?

Why it matters: Helps understand competitive landscape and potential differentiation strategies Expected answer: Mid-tier market position with a focus on simplicity Impact on approach: Would influence whether to lean towards simplicity or advanced features

• Business Context: Based on Fidelity's overall strategy, I'm curious about the revenue model for Fidelity Go. Is it primarily fee-based, or are there other monetization strategies in place?

Why it matters: Aligns solution with business objectives and revenue streams Expected answer: Primarily fee-based with potential for upselling to other Fidelity products Impact on approach: Would guide feature prioritization based on revenue potential

• User Impact: Considering user segmentation, I'm wondering what percentage of Fidelity Go users are requesting more advanced features?

Why it matters: Helps quantify the demand and potential impact of adding complexity Expected answer: A significant minority, perhaps 20-30% of active users Impact on approach: Would influence the balance between maintaining simplicity and adding advanced options

• Technical: Given the existing architecture, I'm curious about the technical feasibility of implementing a tiered feature system within Fidelity Go.

Why it matters: Determines the scope and timeline for potential solutions Expected answer: Possible but would require significant development effort Impact on approach: Would impact the phasing and prioritization of feature additions

• Resource: Considering the potential scope of changes, what's our current team capacity for taking on this project?

Why it matters: Helps determine the realistic timeline and resource allocation Expected answer: Limited capacity with competing priorities Impact on approach: Would influence the scale and timing of proposed solutions