How can Celonis balance simplifying the UI for new users versus maintaining advanced features for power users?

Introduction

Balancing simplicity for new users with advanced features for power users is a critical trade-off for Celonis. This scenario involves optimizing the user interface to cater to diverse user needs while maintaining product effectiveness. I'll analyze this trade-off by examining user segments, product goals, and potential solutions.

Step 1

Clarifying Questions (3 minutes)

• Based on Celonis' market position, I'm thinking this UI simplification might be part of a broader user acquisition strategy. Could you share more about our current user growth targets and how they relate to this initiative?

Why it matters: Helps align the solution with overall business objectives Expected answer: Aggressive growth targets for new users in the next 12 months Impact on approach: Would prioritize new user experience while carefully managing power user retention

• Considering the complexity of process mining, I'm assuming our power users are critical to our revenue. Can you provide a breakdown of revenue contribution between new and power users?

Why it matters: Informs the balance between simplification and advanced feature retention Expected answer: Power users contribute significantly more per user, but new user segment is growing Impact on approach: Would necessitate a phased approach to UI changes, preserving key advanced features

• Given the technical nature of our product, I'm curious about the current onboarding process. How long does it typically take for a new user to become proficient with our core features?

Why it matters: Helps identify pain points in the current user journey Expected answer: Several weeks to months, depending on user background Impact on approach: Would focus on streamlining early user experience and providing progressive complexity

• Thinking about our development resources, I'm wondering about our current team structure. Do we have dedicated teams for UI/UX and advanced feature development?

Why it matters: Influences the feasibility of implementing a dual-track development approach Expected answer: Separate teams with some overlap Impact on approach: Would suggest a collaborative approach with shared OKRs between teams

• Considering the potential impact on our existing users, I'm curious about our current user feedback mechanisms. How do we currently gather and prioritize feature requests from power users?

Why it matters: Ensures we maintain value for our most engaged users Expected answer: Regular surveys and user advisory board meetings Impact on approach: Would incorporate power user feedback into the UI simplification process