Topic starter
06/11/2026 6:40 pm
TL;DR: IAM data management is breaking under wider application estates, manual fulfilment, and rigid IGA deployments, according to READI, with a cited survey finding 51% of respondents blamed process changes for distressed projects. The governing issue is no longer tooling alone but whether identity programmes can adapt workflows, coverage, and data flows without redesigning the business around the platform.
Editorial analysis by NHI Mgmt Group, based on content published by READI: “Connecting The Dots: Why IAM Data Management Needs Agile Automation”.
By the numbers:
- 51% of respondents said the main reason for their IGA project being in distress was having to change existing business processes to fit the technology solution.
Key questions
Q: How should teams reduce manual fulfilment in identity programmes?
A: Start by identifying the access requests that recur often enough to standardise.
Q: Why do narrow IGA deployments create governance gaps?
A: Narrow IGA deployments create governance gaps when they only cover a subset of systems, identities or entitlement types, leaving unmanaged accounts, manual spreadsheets and out-of-band approvals outside review.
Q: What is the best way to automate identity data flows?
A: The best way to automate identity data flows is to connect source systems to a governance or provisioning layer using authoritative sources for people, roles and entitlement data.
Practitioner guidance
- Map the disconnected estate first Inventory the applications, services, and manual fulfilment paths that sit outside the core governance tool so you know where policy is not enforced end to end.
- Reduce process redesign pressure Preserve existing business workflows where they already work and automate around them instead of forcing teams into a new operating model for every application.
- Measure coverage as a control metric Track how many entitlements, request paths, and review steps are still handled through offline tickets or custom code rather than governed flows.
Bottom line: IAM data management fails when identity workflows, application coverage, and fulfilment paths stay fragmented across tools and manual processes.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Identity data fabric is now a control problem, not a tooling preference. Once governance spans SaaS, on-prem systems, APIs, and microservices, narrow application coverage stops being an implementation detail and starts shaping risk. A fragmented fabric forces exceptions into ticketing, custom glue code, and offline fulfilment, which weakens both auditability and control consistency. The practical conclusion is that identity programmes should be judged on estate-wide operability, not on whether the core platform is technically installed.
A question worth separating out:
Q: How do teams know whether identity governance is actually complete across the estate?
A: They do not rely on workflow completion alone. They check whether every in-scope application can be provisioned, reviewed, recertified, and revoked through a governed process with evidence. If even one material application sits outside that cycle, governance completeness has not been achieved.
👉 Read our full editorial: IAM data management needs agile automation as scope outgrows IGA