The Broadcom acquisition of VMware is the most significant enterprise infrastructure transaction of the decade. Its implications extend well beyond VMware's product portfolio.
Most enterprise AI programmes have delivered incremental automation rather than transformational business outcomes. The question is why, and what the organisations that are succeeding have done differently.
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.
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.
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.
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.
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.
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.
The hybrid cloud debate is framed as a technical question of workload placement and latency. The real decisions are strategic: what you own, what you consume, and what that means for cost, talent, and vendors.
Multi-cloud creates an accountability gap: no single team owns the full picture. Closing it is a governance decision, not a tool purchase, and only a few patterns actually work.
