What factors are contributing to the increased time-to-value for SailPoint's IdentityIQ deployments in the past 6 months?

Introduction

SailPoint's IdentityIQ deployments have experienced increased time-to-value over the past 6 months, raising concerns about product efficiency and customer satisfaction. This analysis will systematically identify, validate, and address the root causes while considering both immediate and long-term implications for the product and organization.

I'll approach this issue by first clarifying the context, then ruling out external factors before diving deep into the product ecosystem, metric breakdown, and data-driven hypothesis generation. We'll then conduct a thorough root cause analysis, propose validation methods, and outline a comprehensive resolution plan.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might have been recent changes to the deployment process. Have there been any significant updates to IdentityIQ's deployment methodology or tools in the last 6-9 months?

Why it matters: Recent changes could directly impact deployment efficiency. Expected answer: Yes, there have been some updates to streamline the process. Impact on approach: If confirmed, we'd focus on these changes as potential root causes.

• Considering the complexity of identity management solutions, I'm wondering about customer preparedness. Has there been any shift in the types of customers or their level of technical readiness in recent deployments?

Why it matters: Customer readiness significantly affects deployment time. Expected answer: There's been an increase in less technically prepared customers. Impact on approach: If true, we'd look into improving pre-deployment customer education and support.

• Thinking about resource allocation, I'm curious about any changes in the deployment team. Has there been any significant turnover or restructuring in the professional services or deployment teams recently?

Why it matters: Team changes can impact deployment efficiency and knowledge transfer. Expected answer: Some turnover, but within normal ranges. Impact on approach: If higher than expected, we'd focus on knowledge retention and team training strategies.

• Considering potential system complexities, I'm wondering about the scale of recent deployments. Has there been a shift towards larger, more complex implementations in the past 6 months?

Why it matters: Larger implementations naturally take longer and could skew the average time-to-value. Expected answer: Mix of deployment sizes remains consistent. Impact on approach: If there's a shift, we'd need to segment our analysis by deployment size.

• Reflecting on the metric itself, I'm curious about its consistency. Has the definition or measurement method for "time-to-value" remained constant over the past year?

Why it matters: Changes in metric definition could lead to misinterpretation of the data. Expected answer: No changes to the metric definition. Impact on approach: If changed, we'd need to recalibrate our analysis based on the new definition.