Notifications
Clear all
Topic starter
11/08/2026 3:21 pm
TL;DR: IAM programmes fail when organisations treat them as tool selections instead of business transformations, according to Fischer Identity. Executive sponsorship, project management, and stakeholder mapping are the structural inputs that determine whether lifecycle automation, governance, and adoption hold together.
NHIMG editorial — based on content published by Fischer Identity: Building a Strong Foundation for IAM: Why Executive Sponsorship, Project Management, and Stakeholder Identification Matter
Questions worth separating out
Q: How should security teams structure an IAM programme before selecting technology?
A: Start with executive sponsorship, programme ownership, and stakeholder mapping.
Q: Why do IAM initiatives often stall even when the technology works?
A: Because technology is only one part of the control system.
Q: What do teams get wrong about change management in IAM?
A: They often treat change management as an administrative update rather than a security event.
Practitioner guidance
- Define an executive sponsor with decision authority Select a sponsor who can resolve cross-functional conflicts, secure resources, and frame IAM as a business programme rather than an IT side project.
- Assign a dedicated IAM project manager Use one person to coordinate dependencies across lifecycle automation, account claim design, external identities, and governance milestones.
- Map stakeholder ownership before requirements gathering Document which teams own authoritative source data, policy enforcement, application impacts, and end-user adoption before the design phase begins.
What's in the full article
Fischer Identity's full blog covers the operational detail this post intentionally leaves for the source:
- How the University of Virginia example was used to frame executive backing and programme alignment.
- The specific IAM workstreams named by the vendor, including source system alignment and external identity management.
- The vendor's view of how leadership, project management, and stakeholder engagement translate into adoption outcomes.
👉 Read Fischer Identity's blog on executive sponsorship and IAM programme foundations →
IAM program foundations: what leadership and structure teams need?
Explore further
11/08/2026 3:32 pm
IAM failures usually begin as governance failures, not platform failures. Organisations often overestimate the value of feature selection and underestimate the cost of missing authority, ownership, and cross-functional coordination. When the programme lacks a sponsor and a delivery lead, the result is fragmented identity work that cannot survive competing business priorities. The practical conclusion is that IAM maturity begins with operating model design, not procurement.
A question worth separating out:
Q: Who should own IAM governance in practice?
A: IAM governance should sit with identity, security, and application owners together, because each owns a different part of the access lifecycle. Security defines the control standard, application teams understand entitlement need, and identity teams enforce the process. Without shared accountability, access reviews and deprovisioning lose force.
👉 Read our full editorial: Executive sponsorship is the real foundation of IAM program success
