For Scalable Capital's mobile app, should development resources focus on adding new features to increase user engagement or on simplifying the interface to improve ease of use for less tech-savvy clients?

Introduction

For Scalable Capital's mobile app, we're facing a critical trade-off between adding new features to increase user engagement and simplifying the interface to improve ease of use for less tech-savvy clients. This decision will significantly impact our product strategy, user experience, and ultimately, our business growth. I'll analyze this trade-off by examining our product understanding, key metrics, and potential experiments to inform our decision.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking our app caters to both experienced investors and newcomers. Could you confirm our current user demographics and their investment experience levels?

Why it matters: Helps tailor our approach to the right user segments Expected answer: Mix of experienced and novice investors, skewing towards younger, tech-savvy users Impact: Would influence whether we prioritize advanced features or simplification

• Business Context: Based on our revenue model, I assume we earn through assets under management or transaction fees. How does user engagement directly tie to our revenue streams?

Why it matters: Aligns product decisions with business objectives Expected answer: Higher engagement leads to more frequent trades or larger investments Impact: Might favor adding features if they directly drive revenue-generating actions

• User Impact: I'm thinking about our user retention rates. How do they differ between tech-savvy and less tech-savvy users?

Why it matters: Identifies which user segment needs more attention Expected answer: Lower retention among less tech-savvy users Impact: Could prioritize interface simplification to improve retention of this segment

• Technical: Considering our current tech stack, how complex would it be to implement new features versus redesigning the interface for simplicity?

Why it matters: Assesses feasibility and resource requirements Expected answer: New features are easier to implement than a full interface overhaul Impact: Might favor adding features if simplification requires significant technical effort

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

Why it matters: Helps prioritize short-term vs. long-term strategies Expected answer: Looking for impact within the next two quarters Impact: Could influence whether we opt for quick wins (features) or long-term improvements (simplification)