Notifications
Clear all
Topic starter
08/07/2026 6:53 pm
TL;DR: Service management is shifting from reactive support to AI-assisted, continuous governance as organisations face higher operational complexity, tighter cost pressure, and sovereignty demands, according to Efecte and Gartner’s 2026 priorities. That shift matters because identity, access, and workflow control now sit inside the same operating model, not separate queues.
NHIMG editorial — based on content published by Efecte: Strategic shift, 2026, and the rise of intelligent service management
By the numbers:
- Gartner's Agenda 2026 says reducing operational costs is the top priority for CIOs.
- Gartner predicts that by 2030, 75% of European companies will move virtual workloads to regional or sovereignty-assured alternatives.
- 100% visibility into usage and spend enables real-time software optimisation.
Questions worth separating out
Q: How should teams govern AI-assisted service workflows without losing accountability?
A: Teams should treat each automated or AI-assisted workflow step as a governed execution path with a named owner, an auditable approval boundary, and clear revocation logic.
Q: Why do service management platforms create identity governance risk at scale?
A: They create risk because they concentrate approvals, fulfilment, and exception handling into one operational layer, which increases the number of identities and delegated rights that can act without direct human oversight.
Q: What signals show that automation has outgrown existing access controls?
A: The clearest signals are unowned service accounts, repeated approval exceptions, workflow steps that bypass normal review, and regional workload movement that no longer matches policy.
Practitioner guidance
- Map identity controls to automated fulfilment paths Inventory which service workflows now auto-create access, approve exceptions, or trigger downstream actions.
- Separate human approvals from machine execution rights Define which steps in HR, finance, and IT workflows may be initiated by humans, which may be executed by service accounts, and which require explicit review.
- Extend sovereignty controls into identity policy Align region, residency, and workload placement decisions with the identities that move or process data across environments.
What's in the full article
Efecte's full article covers the operational detail this post intentionally leaves for the source:
- The article’s full breakdown of the five 2026 service-management shifts and how they connect to operational pressure
- The vendor’s framing of AI as an execution layer rather than only a decision-support layer
- The discussion of software-spend visibility and continuous control in more implementation-oriented terms
- The sovereignty and geopatriation arguments that are only summarised here at a strategic level
👉 Read Efecte's analysis of intelligent service management in 2026 →
Smart service management in 2026: what changes for IAM teams?
Explore further
08/07/2026 7:14 pm
Intelligent service management is becoming an identity governance problem, not just an operations problem. The article’s central claim is that service delivery, automation, and cost control are converging into one control plane. That convergence matters because every automated fulfilment path depends on identity, entitlement, and approval logic that can fail silently if governance is still organised around tickets instead of execution. Practitioners should treat service management redesign as identity programme redesign.
A few things that frame the scale:
- Organisations maintain an average of 6 distinct secrets manager instances, creating fragmentation that undermines centralised control, according to The State of Secrets in AppSec.
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases.
A question worth separating out:
Q: Who should own governance when AI and service management overlap?
A: Ownership should sit with the team responsible for the business outcome, but the identity and security functions must define the control model. That means service owners, IAM, and platform teams need a shared model for delegation, logging, lifecycle review, and rollback before automation expands further.
👉 Read our full editorial: AI-driven service management is reshaping 2026 governance
