For E*TRADE's mobile app, should we focus on adding more advanced charting features or simplifying the interface for newer investors?

Introduction

For E*TRADE's mobile app, we're facing a critical trade-off between adding advanced charting features or simplifying the interface for newer investors. This decision will significantly impact our user experience, market positioning, and potentially our revenue streams. I'll analyze this trade-off by examining our product goals, user segments, technical considerations, and potential business impacts.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about our current user base composition. Could you share the breakdown between experienced traders and newer investors using our mobile app?

Why it matters: Helps determine which user segment to prioritize Expected answer: 60% experienced, 40% newer investors Impact: A higher percentage of newer investors might lean us towards simplification

• Business Context: Based on our revenue model, I assume a significant portion comes from trading fees. How does user engagement in the mobile app correlate with overall trading volume?

Why it matters: Connects app features to revenue generation Expected answer: Strong positive correlation between app engagement and trading volume Impact: If true, might justify advanced features to increase engagement of high-volume traders

• User Impact: I'm curious about user retention rates. Do we see a difference in churn between newer investors and experienced traders?

Why it matters: Identifies which user segment might need more attention Expected answer: Higher churn rate among newer investors Impact: Higher new investor churn would support interface simplification

• Technical: Regarding our current app architecture, how modular is it? Could we potentially implement both advanced charting and a simplified interface as toggleable options?

Why it matters: Explores possibility of a hybrid solution Expected answer: Moderately modular, but significant work required for toggle feature Impact: If feasible, could inform a compromise solution

• Timeline: Given our product roadmap, what's our timeline for implementing and testing these changes?

Why it matters: Helps prioritize short-term vs. long-term strategies Expected answer: 3-6 months for development and initial testing Impact: Shorter timeline might favor simpler interface changes; longer allows for more complex features