Topic starter
06/09/2026 5:18 pm
TL;DR: Enterprise technology spending reached nearly $4 trillion in 2025, and Arxan Technologies’ analysis says the bigger story was execution strain: cloud, AI, modernization, and software investments multiplied faster than organisations could absorb them. The result is a governance problem for capacity, dependency management, and adaptive planning, not simply a budget problem.
Editorial analysis by NHI Mgmt Group, based on content published by Arxan Technologies: “Two Tales of $4 Trillion: The Reality Behind 2025’s IT Spend”.
Key questions
Q: What breaks when transformation programmes outpace execution capacity?
A: Governance breaks first, because teams lose the ability to validate dependencies, absorb change, and keep controls aligned with the environment.
Q: Why does parallel cloud, AI, and modernization work create operational risk?
A: Parallel work raises risk because each change can alter the assumptions behind other systems, including access paths, telemetry, service ownership, and workload behaviour.
Q: How can teams tell whether adaptive planning is actually working?
A: It is working when decisions reflect current capacity, dependencies, and risk signals rather than stale programme assumptions.
Practitioner guidance
- Measure execution capacity alongside transformation spend Track how many major changes teams can validate, absorb, and govern per quarter, not just how much is being funded.
- Build dependency maps for parallel change programmes Document which applications, data flows, identities, and services each initiative touches before it starts.
- Align access governance with live operating conditions Tie certification, privilege review, and workload onboarding to current architecture and service ownership rather than annual planning assumptions.
Bottom line: The article's core point is that record spend did not remove the constraint on delivery, because organisational capacity remained the limiting factor.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/09/2026 5:19 pm
Execution capacity is becoming a governance control, not a staffing metric. The article shows that organisations can spend aggressively and still fail to deliver if validation, oversight, and dependency handling do not scale at the same pace. That is a structural governance problem, not a temporary resourcing issue. Practitioners should treat capacity as part of control design.
A few things that frame the scale:
- Gartner predicts that by 2028, 33% of enterprise software applications will include agentic AI, up from less than 1% in 2024, and that 15% of day-to-day work decisions will be made autonomously.
A question worth separating out:
Q: Should security and IAM teams prioritise capacity governance over adding more tools?
A: Yes, when the problem is not a missing product but an organisation that cannot absorb change cleanly. More tooling does not fix overextended teams, unclear dependencies, or control processes that lag the pace of transformation. Capacity governance should come first because it determines whether existing controls can operate effectively at scale.
👉 Read our full editorial: Enterprise IT spend hit $4 trillion, but execution capacity lagged