How can Hexagon PPM balance the customization options in its EcoSys Enterprise Project Performance software with the need for standardization and ease of implementation across diverse client organizations?

Introduction

Balancing customization options with standardization and ease of implementation in Hexagon PPM's EcoSys Enterprise Project Performance software presents a critical trade-off. This scenario involves weighing the benefits of tailored solutions against the efficiency of a more standardized approach across diverse client organizations. I'll analyze this trade-off through several key lenses, including product understanding, metrics identification, experimentation, and decision-making frameworks.

Step 1

Clarifying Questions (3 minutes)

• Based on the industry trends, I'm thinking customization is a key differentiator in enterprise software. Could you share how important customization has been for winning and retaining clients in the past?

Why it matters: Helps gauge the strategic importance of customization Expected answer: Customization has been crucial for several large accounts Impact on approach: Would prioritize maintaining some level of customization

• Considering our revenue model, I assume there's a balance between implementation fees and ongoing subscription revenue. What's the current split, and how might standardization affect this?

Why it matters: Informs the financial implications of our decision Expected answer: 30% implementation, 70% subscription, with potential for standardization to reduce implementation revenue but increase scalability Impact on approach: Would need to consider how to offset potential implementation revenue loss

• Looking at user behavior, I'm curious about the most commonly customized features. Can you share which aspects of EcoSys clients tend to modify most frequently?

Why it matters: Identifies areas where standardization might have the most impact Expected answer: Project workflow customization and reporting are most common Impact on approach: Would focus on standardizing less-modified features first

• From a technical perspective, I'm wondering about the current architecture's flexibility. How modular is the system, and what's our capacity for creating standardized modules that still allow some customization?

Why it matters: Determines the feasibility of a hybrid approach Expected answer: Moderately modular, with potential for improvement Impact on approach: Would explore a phased approach to increase modularity

• Considering our implementation team's capacity, how would standardization impact our ability to take on new clients? Are we currently constrained by implementation resources?

Why it matters: Assesses potential for scaling and resource allocation Expected answer: Currently at 80% capacity, standardization could significantly increase new client onboarding Impact on approach: Would prioritize standardization efforts that reduce implementation complexity