Should Okta prioritize expanding integrations or improving existing core functionalities?

Introduction

The trade-off between expanding integrations and improving existing core functionalities is a critical decision for Okta's product strategy. This scenario involves balancing the breadth of our product ecosystem against the depth and quality of our core offering. I'll analyze this trade-off by examining the business context, user impact, technical considerations, and resource allocation to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Okta's current market position. Could you share any recent changes in our competitive landscape or customer demands that might be driving this trade-off consideration?

Why it matters: Helps prioritize based on market pressures Expected answer: Increased competition in core IAM space Impact on approach: May lean towards improving core functionalities

• Business Context: Based on our revenue model, I assume expanding integrations could open new revenue streams. How does our current revenue split between core product and integration-based services look?

Why it matters: Informs potential financial impact of each option Expected answer: 70% core, 30% integration-based Impact on approach: Balanced approach might be necessary

• User Impact: Considering our user segments, I'm curious about the adoption rates of our existing integrations. What percentage of our enterprise customers are using multiple integrations?

Why it matters: Indicates demand for expanded integrations Expected answer: 60% use 3+ integrations Impact on approach: Could justify focus on expansion if high

• Technical: Regarding our current architecture, how modular is our system for adding new integrations versus refactoring core functionalities?

Why it matters: Affects feasibility and resource requirements Expected answer: Modular for integrations, complex for core Impact on approach: Might favor integration expansion if easier

• Resource: Thinking about our team structure, how are our engineering resources currently allocated between core product and integration teams?

Why it matters: Indicates current focus and potential for reallocation Expected answer: 60% core, 40% integrations Impact on approach: Could inform realistic timelines for each option