Should Anaplan prioritize adding more advanced modeling capabilities to its Connected Planning platform or focus on simplifying the user interface for broader adoption?

Introduction

The trade-off between adding advanced modeling capabilities and simplifying the user interface for Anaplan's Connected Planning platform presents a critical decision point. This scenario encapsulates the classic tension between power and accessibility in enterprise software. I'll analyze this trade-off by examining product understanding, stakeholder impacts, metrics, experimentation, and decision frameworks to arrive at a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Anaplan's current market position. Could you share insights on our market share and primary competitors?

Why it matters: Helps gauge competitive pressure and potential differentiation strategies. Expected answer: Mid-market share, competing with legacy systems and newer cloud-based solutions. Impact: High market share might favor simplification, while low share could justify advanced features.

• Business Context: Based on our revenue model, I assume subscription-based pricing is key. How does user adoption impact our revenue growth?

Why it matters: Aligns product strategy with business objectives. Expected answer: Direct correlation between user adoption and revenue. Impact: Strong link would prioritize UI simplification for broader adoption.

• User Impact: Considering our user base, I'm curious about the split between power users and casual planners. What's the current ratio?

Why it matters: Balances feature depth with accessibility. Expected answer: 20% power users, 80% casual users. Impact: High power user percentage might justify advanced modeling focus.

• Technical: Regarding our platform architecture, how modular is it for feature additions vs. UI overhauls?

Why it matters: Assesses technical feasibility and resource allocation. Expected answer: Moderately modular, requiring significant effort for both options. Impact: High modularity might allow pursuing both paths simultaneously.

• Resource: Thinking about our development capacity, what's our current team size and skill distribution?

Why it matters: Determines feasibility of parallel development tracks. Expected answer: 50-person team, balanced skills but limited UI/UX specialists. Impact: Limited UI expertise might favor focusing on modeling capabilities first.