For Esri's ArcGIS Enterprise, should we invest more in cloud-native capabilities or continue enhancing on-premises deployment options to cater to security-conscious clients?

Introduction

The trade-off we're examining today is whether to invest more in cloud-native capabilities for Esri's ArcGIS Enterprise or continue enhancing on-premises deployment options for security-conscious clients. This decision is crucial for Esri's product strategy and market positioning. I'll analyze this trade-off by examining the product context, stakeholder impacts, key metrics, and potential experiments to inform our decision.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market landscape for GIS solutions. Could you share more about our competitors' cloud vs. on-premises offerings and how they're positioning themselves?

Why it matters: Helps understand competitive pressures and market trends Expected answer: Mix of cloud and on-premises offerings, with a trend towards cloud Impact on approach: Would influence how aggressively we need to move towards cloud-native capabilities

• Business Context: Based on our revenue model, I assume there's a significant portion coming from on-premises deployments. What's the current revenue split between cloud and on-premises, and how has it been trending over the past 2-3 years?

Why it matters: Informs the financial impact of shifting focus Expected answer: On-premises still dominant but cloud growing faster Impact on approach: Would help balance short-term revenue protection with long-term growth

• User Impact: Considering our security-conscious clients, what specific concerns or requirements have they expressed regarding cloud adoption?

Why it matters: Identifies potential barriers to cloud migration Expected answer: Data sovereignty, compliance, and control concerns Impact on approach: Would guide development of cloud features addressing these specific needs

• Technical: Regarding our current architecture, how modular is it in terms of supporting both cloud-native and on-premises deployments from a single codebase?

Why it matters: Affects the feasibility and efficiency of supporting both options Expected answer: Some modularity, but significant work needed for full cloud-native support Impact on approach: Would influence the timeline and resource allocation for cloud-native development

• Resource: What's our current team composition in terms of cloud vs. on-premises expertise, and how easily can we scale up cloud development capabilities?

Why it matters: Determines our ability to execute on cloud-native initiatives Expected answer: Strong on-premises expertise, growing cloud capabilities Impact on approach: Would impact the pace of cloud-native development and potential need for hiring or training