Notifications
Clear all
Topic starter
25/06/2026 5:22 pm
TL;DR: Customer success in identity security is measured by adoption, outcomes, and candid feedback rather than sentiment alone, according to SailPoint, and its community now includes nearly 100K members. That framing matters because identity programmes fail when engagement looks healthy but operational outcomes are weak.
NHIMG editorial — based on content published by SailPoint: Customer success in identity security depends on outcomes
By the numbers:
- SailPoint has built a community of nearly 100K members
Questions worth separating out
Q: How should identity teams measure customer success in an IAM programme?
A: They should measure whether the platform is being adopted, whether control coverage is increasing, and whether the programme is improving governance outcomes.
Q: Why does peer feedback matter in identity security programmes?
A: Peer feedback matters because it surfaces implementation friction, misunderstood controls, and governance gaps that internal teams may miss.
Q: How can training improve identity governance outcomes?
A: Training improves outcomes when it gives administrators and governance owners a shared operating baseline for access reviews, lifecycle actions, and privileged access decisions.
Practitioner guidance
- Measure identity success by outcomes, not sentiment Define programme health using adoption rates, policy coverage, review completion, and issue resolution rather than customer happiness proxies.
- Build a structured feedback loop with operators and peers Create a mechanism for architecture, operations, and governance teams to capture implementation lessons and recurring friction points.
- Treat education as part of the identity control stack Map required training to the people who administer, approve, and govern identity controls.
What's in the full article
SailPoint's full blog covers the operational detail this post intentionally leaves for the source:
- How Identity University is positioned for customers, partners, and public enrolment in practice
- The customer-success philosophy behind SailPoint's internal support and enablement model
- Why the company frames feedback, dialogue, and community participation as part of the customer experience
- What SailPoint says about the role of employee culture in delivering identity outcomes
👉 Read SailPoint's blog on customer success, community, and Identity University →
Customer success in identity security: what actually drives outcomes?
Explore further
25/06/2026 6:00 pm
Outcome metrics are the only meaningful customer-success measure in identity security. Satisfaction can coexist with incomplete adoption, weak policy enforcement, or unresolved lifecycle gaps. The stronger indicator is whether the programme is changing access behaviour and governance outcomes in production. For practitioners, that means measuring control use, not just customer sentiment.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: What should teams evaluate in a vendor enablement programme?
A: Teams should evaluate whether the enablement model helps operators adopt the controls correctly, whether it reduces support friction, and whether it supports consistent governance across teams. If training and community resources do not improve execution, they are not contributing to programme maturity. Enablement quality is part of operational readiness.
👉 Read our full editorial: Customer success in identity security depends on outcomes
