Should Bentley Systems prioritize expanding the features of MicroStation to attract new users or focus on simplifying the interface to improve retention of existing customers?

Introduction

The trade-off we're examining today is whether Bentley Systems should prioritize expanding MicroStation's features to attract new users or focus on simplifying the interface to improve retention of existing customers. This scenario touches on the classic product management challenge of balancing growth with user satisfaction. I'll approach this by analyzing the current product state, potential impacts, and data-driven decision-making processes.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming MicroStation is a mature product in the CAD/BIM space. Could you confirm its current market position and primary user base?

Why it matters: Helps frame the urgency of new user acquisition vs. retention Expected answer: Market leader with a significant professional user base Impact: If not a leader, might lean towards feature expansion

• Business Context: Based on industry trends, I'm thinking subscription revenue is key. What's our current revenue model and how does it factor into this decision?

Why it matters: Aligns solution with financial objectives Expected answer: Subscription-based with some perpetual licenses Impact: Heavy subscription focus would prioritize retention

• User Impact: Considering the complexity of CAD software, I'm guessing our user base is primarily professionals. Can you describe our main user segments and their skill levels?

Why it matters: Determines the balance between power features and usability Expected answer: Mix of expert users and newer professionals Impact: More diverse user base might favor interface simplification

• Technical: Given the robust nature of MicroStation, I imagine there are significant technical considerations for both options. What's our current technical debt situation?

Why it matters: Influences feasibility and timeline of changes Expected answer: Some legacy code, but generally manageable Impact: High technical debt might favor interface improvements over new features

• Resource: Considering the scope of both options, I'm curious about our team capacity. Do we have separate teams for feature development and UX/UI, or is it a shared resource?

Why it matters: Affects our ability to pursue both paths simultaneously Expected answer: Shared resources with some specialization Impact: Dedicated teams might allow for parallel efforts