Most organisations aren’t struggling to start with cloud. UK customers spent £10.5bn on cloud services in 2024, with spend growing by nearly 30% a year since 2020.
They’ve already proven they can deliver it. Platforms are in place, workloads have been migrated, and delivery teams understand how to build and release into cloud environments.
The difficulty comes later.
Why scale creates complexity
As cloud adoption expands, the environment becomes harder to manage as a whole. More teams contribute. More services are introduced. Change becomes continuous rather than contained. And what worked at the level of individual projects becomes harder to sustain across the estate.
This is where consistency starts to break down.
The common assumption is that complexity emerges because cloud environments become technically larger. In reality, the bigger challenge is structural. Cloud is often delivered through project models designed for fixed outcomes and finite timelines, while cloud itself behaves as a continuously evolving system.
Each project may succeed in isolation, but every project introduces new decisions, interpretations of standards, governance approaches and operational practices. As cloud adoption grows, organisations are not simply managing more technology. They are managing the accumulated complexity of hundreds of disconnected decisions.
This is why complexity emerges structurally rather than operationally. The technology is scaling, but the operating model behind it remains fragmented.
The problem isn't that organisations have too much cloud. The problem is that they are trying to govern an increasingly dynamic system through structures designed for temporary change.
Why automation alone doesn't solve the problem
Automation improves part of the problem. Standard environments, pipelines, and policy-based configurations help reduce variation in known scenarios. They make delivery more efficient, where conditions are predictable.
But they don’t resolve the underlying issue.
Control is still applied alongside delivery rather than through it. It remains dependent on periodic review and manual intervention, which makes it difficult to sustain as change increases.
At scale, the question changes.
It is no longer whether teams can deploy. It is whether the organisation can maintain control and visibility as the environment evolves, without increasing friction.
This is where a different approach is required.
From cloud projects to cloud operating models
Cloud needs to move from being delivered as projects, to being run as an operating model.
In this model, control becomes part of how work happens. Standards are applied as changes are made.
This shifts cloud from being something that is periodically delivered to something that is continuously managed. Capabilities become embedded rather than activities that sit alongside delivery. As a result, organisations can scale cloud adoption without scaling complexity, maintaining control and consistency even as platforms, services and delivery teams continue to evolve.
The environment is managed as a system rather than a set of independent initiatives.
An operating model is not a framework. It is the reality of how cloud work happens day-to-day. It defines how requests are initiated, how standards are applied, how changes move into production, and how the environment is monitored and improved over time.
When this is in place, safe and consistent outcomes become repeatable. Progress starts to build rather than reset.
Organisations that move forward do not remove governance. They change how it works.
They reduce reliance on manual review and increase the consistency of decisions across the estate. They move from aligning work after it has happened to shaping it as it happens.
This is where an operating model starts to take hold.
Turning intent into execution
However, defining that model is only part of the answer.
The real challenge is making it work in practice, day after day, across a constantly changing environment.
Most organisations are not there yet.
Control is still something that is documented and enforced after the fact, rather than something that runs continuously.
The next step is moving from intent to execution.
If cloud is still being delivered as a series of projects, the next step is understanding how well that approach will scale. Many of the challenges in cost, risk and consistency only become visible as environments grow.
A structured assessment can help identify where control starts to break down and where it needs to be embedded into delivery.
However, recognising the need for a cloud operating model is only the beginning. Defining an operating model on paper does not guarantee that it works consistently in practice.
The next challenge is execution. How do organisations ensure that controls, standards, policies and governance operate continuously across a constantly changing environment rather than depending on manual intervention?
That is where the conversation moves from operating models to control systems.
Is your cloud operating model ready to scale?
Many organisations only recognise the limits of project-based cloud delivery when complexity, cost, and governance challenges begin to impact delivery.
A structured assessment can help identify where control is becoming dependent on manual intervention, where consistency is starting to break down, and where an operating model approach could create greater resilience.
Speak to our cloud specialists about assessing your cloud operating model.
Read more in our cloud series here.