A cloud operating model asks IT to shift from owner of infrastructure to provider of services, and from gatekeeper to enabler. Making that work means designing services around the distinct personas IT actually serves.
Architecture cannot, by itself, let hundreds of product teams deliver cloud-native software at speed. The platform team is the organisational structure that can, and a few conditions separate the ones that accelerate delivery from the ones that become bottlenecks.
Cloud vendor sprawl accumulates through organic growth, shadow IT, and team preference, faster than awareness of it. Consolidation that works starts from capability requirements, not cost reduction.
Each cloud provider arrives with its own tooling, billing, access controls, and team, forming silos that mirror the datacentre era but cost more and are harder to govern. The operating model is the structural answer.
Boards approve multi-cloud for sound strategic reasons. Engineering teams inherit incompatible control planes, fragmented security, and cross-cloud complexity. Closing that gap takes specific platform, governance, and skills investments.
Cloud programmes are often governed by datacentre-era frameworks: change boards, long approvals, capacity planning, project funding. They are structurally incompatible with cloud, and redesigning governance is a prerequisite, not a nice-to-have.
Migration is a single dimension, and it tells you little about value. The Cloud Operating Model defines three competencies, Service Delivery, Operations, and Governance, and a programme's maturity is the balance across all three.
Microservices promise independent deployability and scalability, and often deliver a distributed complexity worse than the monolith they replaced. The escape is service boundaries drawn around domains, not technical decomposition.
The common DevSecOps failure is treating it as DevOps with security tools added to the pipeline. Real DevSecOps redesigns who owns security decisions and when, and the operational gap decides whether security enables delivery or blocks it.
Most cloud strategies fail because they start with the cloud and reason backwards to a business case. The logic only works forwards: business strategy drives application strategy, which drives cloud strategy, operationalised through the operating model.
