Most cloud programmes are graded on a single question: did the workloads move? That question is the wrong one, and answering it well tells you almost nothing about whether the cloud is delivering value.
The first article in this series argued that cloud strategy has to be driven by business strategy. This one moves to the next question: once you have a cloud strategy, what determines whether it actually delivers? The Cloud Operating Model framework answers with three distinct competencies, and a programme’s real maturity is not how far it has migrated but how well it has built all three. Migration is movement. These three are what turn movement into value.
Three Competencies, Not One Migration
The three competencies are Service Delivery, Operations, and Governance, and each answers a different question about the cloud programme.
Service Delivery is the ability to provision what teams need on demand, with genuine self-service and developer agility. It answers: can the organisation get value out of the cloud quickly, or does every request still queue behind a human? This is the competency that delivers the speed the cloud was bought for.
Operations is the ability to run what has been provisioned well, optimising performance and cost intelligently across cloud environments. It answers: can the organisation keep the cloud reliable and efficient as it grows, or does scale turn into spiralling cost and fragile systems? This is the competency that makes the cloud sustainable rather than just fast.
Governance is the ability to enforce policy, financial accountability, and compliance without creating so much friction that teams route around it. It answers: can the organisation stay in control without strangling the agility the other two competencies provide? This is the competency that keeps the cloud safe and accountable, and it is the hardest of the three, because done badly it does not just fail. It actively drives the shadow IT it was meant to prevent.
Why Organisations Mature Them in the Wrong Order
Most enterprises build these competencies in the wrong sequence, and the wrong sequence is predictable. They start with Service Delivery, because speed is visible and popular and it is what the cloud was sold on. They reach Operations later, usually when the cost and reliability problems of unmanaged growth become impossible to ignore. And they get to Governance last, often only after a security or compliance incident forces it, by which point retrofitting control onto an established free-for-all is at its most painful.
The right approach is to build the three together, in balance, because each one without the others fails in a characteristic way. Service Delivery without Governance is speed without control, which ends in a security or cost incident. Governance without Service Delivery is control without speed, which ends in shadow IT as teams escape the friction. Operations holds the two in tension over time. A programme strong in one competency and weak in the others is not partially mature. It is unbalanced, and the imbalance is usually what is actually causing its problems.
Building a Board-Level Assessment
The practical value of the three competencies is as an assessment. Instead of asking the single migration question, a board can ask three better ones. On Service Delivery: can our teams get what they need on demand, within guardrails, without waiting on a human gate? On Operations: are we managing performance and cost deliberately across our environments, or reacting to surprises? On Governance: can we enforce policy and accountability without driving people to work around us?
Scored honestly, these three locate a programme far more accurately than a migration percentage ever could. Most enterprises, run through this assessment, find they are strong on Service Delivery, weaker on Operations, and weakest on Governance, which is exactly the unbalanced profile the wrong maturity sequence produces. Naming the imbalance is the start of correcting it.
Three Competencies, One Honest Assessment
The question that actually matters about a cloud programme is not how much has moved but how well the organisation can deliver, operate, and govern what it runs. Service Delivery, Operations, and Governance are the three competencies that turn a migration into a capability, and a programme’s maturity is the balance across all three, not the strength of whichever one came easiest. Before the next cloud investment conversation, score the programme honestly on each, and pay closest attention to the one scoring lowest. It is almost always Governance, and it is almost always the competency quietly deciding whether the other two ever pay off.