Cloud cost has moved from an IT operations concern to a CFO agenda item. Most IT organisations cannot yet have the finance-led governance conversation that follows, and the time to prepare is before it becomes a crisis.
A year of cloud programme experience is an honest test of the operating model frameworks. Cost and platform engineering advanced; the people and governance dimensions are still where most programmes stall.
Shift-left security is now widely accepted in principle and rarely implemented in practice. Four process changes separate organisations that genuinely moved security left from those that relabelled the gate at the end.
The cloud patterns of 2021 point clearly at 2022: cost moving from CFO mandate to engineering discipline, platform engineering as a function, security shifting left, and multi-cloud becoming a governance problem. Four operating model trends, with budget and design implications.
Log4Shell exposed a systemic enterprise risk: dependence on open source components with unknown security postures, embedded deep in production with no reliable inventory. It is a preview of the supply chain challenge, not an anomaly.
Every cloud-native architecture deck ends with a target-state diagram and skips the organisational change required to reach it. The architecture decision and the change decision have to be made together, or the diagram never materialises.
Infrastructure metrics tell you the platform is running, not that the application is delivering value. Cloud-native health needs a business frame: transaction success, user-facing SLOs, and error budgets defined by product impact.
Four shifts are reshaping enterprise infrastructure investment: cost maturity driving consolidation, Kubernetes becoming a platform, platform engineering formalising, and FinOps moving to accountability. A strategic lens for current decisions, not a forecast.
Platform engineering formalises what the best DevOps teams were already building: a governed, developer-friendly internal platform that lets product teams ship without reinventing infrastructure. The formalisation is the point.
Cloud programmes fund infrastructure heavily and skills barely. The gaps that derail them are predictable, and skills should be a strategic capability decision made at the same level as architecture.
