Omada and iC Consult sharpen the case for global IGA delivery

At a glance

What this is: NHI Mgmt Group's analysis, drawing on Omada Identity's report: Omada and iC Consult are extending a long-running IGA relationship across more regions, more specialists, and a dedicated centre of excellence.

Why it matters: It matters because global IGA programmes fail when delivery capacity, integration support and operating-model maturity lag behind governance ambition.

Context

Global identity governance and administration programmes rarely fail because the policy idea is wrong. They fail when the operating model cannot sustain implementation, integration, and support across regions, languages, and local compliance demands. In that sense, delivery capacity becomes part of the control surface, not a separate services layer.

Omada Identity's update is best read as a signal about how complex IGA has become for multinational environments. The article describes a partnership that extends across multiple geographies and uses a dedicated centre of excellence to improve expertise and delivery consistency, which reflects a broader shift from tool selection to lifecycle execution.

Key questions

Q: How should teams judge whether their IGA operating model is ready for global rollout?

A: Teams should test whether the operating model can sustain design, integration, support, and governance decisions across multiple regions without relying on bespoke project effort. If each country needs a different delivery pattern, the programme is not yet ready for global scale. Repeatability, ownership clarity, and support depth matter as much as platform capability.

Q: Why do global IGA programmes fail even when the platform is sound?

A: They fail when delivery capacity, local integration effort, and support ownership are treated as separate from governance. In practice, the control only works if the implementation model can keep policy, process, and technical configuration aligned across regions and business units. A strong platform cannot compensate for inconsistent execution.

Q: What signs show that an IGA programme is too dependent on custom project work?

A: Warning signs include every rollout creating new role definitions, certification scopes, or connector approaches, plus repeated delays when local teams are asked to adopt the same control pattern. That usually means the organisation has not turned governance intent into reusable delivery standards.

Q: What should organisations clarify before relying on external partners for IGA delivery?

A: They should clarify decision rights, support boundaries, escalation paths, and who owns the state of the control after go-live. External delivery can add reach and specialist depth, but accountability for access governance cannot become ambiguous. The internal owner still needs to own the risk and the outcome.

Technical breakdown

Why global IGA delivery becomes a governance problem

Identity governance and administration is not only about workflows for access requests, approvals, and certification. In large enterprises, the control only works if design, configuration, integrations, and support can be delivered consistently across business units and jurisdictions. That makes partner capability part of the practical governance model, especially when the programme must handle hybrid environments, regional operating differences, and change management over time. A product can define the control intent, but the delivery structure determines whether the control is repeatable outside a pilot. This is why global IGA programmes often stall after initial rollout: the implementation model cannot keep pace with the governance scope.

Practical implication: assess whether your IGA operating model can scale beyond one region before treating the platform as ready for enterprise rollout.

What a centre of excellence changes in IGA execution

A centre of excellence is a delivery construct that concentrates reusable expertise, methods, and implementation patterns. In IGA, that matters because entitlement models, role design, certification scope, and connector design are rarely one-size-fits-all. Without a repeatable knowledge base, each rollout becomes a new interpretation exercise, which increases inconsistency and delay. The article's emphasis on more than 40 dedicated specialists points to the fact that implementation quality is often constrained by who can translate governance intent into operational configuration. In practice, the governing question is whether the delivery team can convert policy into stable controls across multiple countries and business units.

Practical implication: standardise IGA design patterns and ownership boundaries so new rollouts do not depend on ad hoc project knowledge.

Why ecosystem delivery now shapes IGA outcomes

Modern IGA programmes depend on more than native product functionality. They need integration with HR systems, directories, cloud platforms, privileged access workflows, and local process owners. That creates an ecosystem problem: the programme has to coordinate product, consulting, managed services, and business accountability at the same time. When a partnership expands across regions, it suggests the market is valuing delivery reach, not just licensing. For practitioners, that means vendor evaluation should include the maturity of the implementation and run-state ecosystem, not merely the feature set. The control objective remains governance, but the execution path is increasingly multi-party.

Practical implication: evaluate the full delivery ecosystem, including integration, support, and managed services, before committing to a global IGA rollout.

NHI Mgmt Group analysis

Global IGA is now an operating-model discipline, not a software procurement decision. The article shows a long-running partnership being formalised around regional delivery scale, specialist depth, and a centre of excellence. That signals a market where governance outcomes depend on the ability to implement and sustain controls across jurisdictions, not just on selecting an IGA platform. Practitioners should treat delivery design as part of control design.

Delivery capacity has become a control dependency for hybrid IGA programmes. Omada's positioning around complex hybrid environments matters because entitlement structures, certification scope, and integration logic all vary by region and business unit. Without repeatable delivery, the same governance policy produces different operational results. The implication is that global IGA programmes need a consistent execution model before they can claim consistent governance.

Partner ecosystems are becoming the real differentiator in enterprise identity governance. The article emphasises joint projects, dedicated specialists, and managed services, which points to a broader industry shift: implementation depth is as important as platform capability. This is especially true where identity governance must coexist with IAM, Zero Trust, and operational support. Practitioners should evaluate whether their ecosystem can carry the programme after go-live.

Global IGA delivery now rewards reusable implementation knowledge over bespoke project heroics. The centre of excellence described in the article is a sign that enterprises want repeatable patterns for roles, certifications, integrations, and support. That reduces variance across deployments and makes operating models more durable. The practical conclusion is straightforward: standardisation is becoming a governance control, not just a project preference.

From our research library:

• Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.

What this signals

Global IGA delivery is becoming an assurance problem. Once identity governance spans multiple regions, the question is no longer whether the control exists in design, but whether it can survive local deployment, support, and change. That makes delivery consistency part of the trust model for the programme.

Reusable implementation knowledge is the new scale lever. Multinational IGA efforts need common patterns for entitlement modelling, certification, and connector onboarding if they want predictable outcomes. Without that reuse, governance quality varies by country and by project team, which weakens the programme over time.

For practitioners

• Assess delivery model maturity Map who is responsible for design, integration, support, and run-state decisions across each region before expanding IGA scope.
• Standardise rollout patterns Create reusable templates for certification scopes, role structures, and connector onboarding so each country deployment does not reinvent the programme.
• Test operating model coverage Validate whether the combined vendor, integrator, and managed-service ecosystem can support both implementation and steady-state governance.
• Review accountability boundaries Define which decisions stay with internal identity owners and which move to external delivery partners before global expansion begins.

Key takeaways

• Global IGA programmes are increasingly judged by delivery consistency, not just by the quality of the underlying platform.
• The article points to scale signals such as more than 110 joint projects, 40 dedicated specialists, and a presence across eight regions.
• Practitioners should treat implementation depth, support coverage, and reusable design patterns as core governance requirements for enterprise IGA.

Key terms

• Identity Governance and Administration (IGA): A framework of policies, processes, and technology to manage and govern digital identities and their access rights. Increasingly extended to cover non-human identities alongside human users.
• Operating Model: An operating model is the practical way a governance programme is run, including decision ownership, workflow design, integrations, and control boundaries. For identity security, the operating model determines whether policy intent survives real execution across human, NHI, and AI-assisted processes.
• Centre of Excellence Model: A centre of excellence model is an operating structure where a specialised team owns policy, tooling, and standards while other teams consume the service through governed workflows. For certificate management, it reduces fragmentation and creates a single point of accountability for lifecycle controls.
• Certification scope: Certification scope is the set of identities, entitlements, or privileges included in an access review campaign. Good scope reduces reviewer fatigue by focusing human attention on the access most likely to be risky, while poor scope turns certification into a box-ticking exercise.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.