This article draws on analysis originally published at cloudcomputing-news.net, referencing a Forrester report on hybrid multi-cloud strategy commissioned by IBM, as well as data from the Everest Group and IDC.
The Cloud Label Problem
“Cloud” has become one of the most overloaded terms in enterprise technology. Vendors routinely attach the label to solutions that are, in practice, little more than traditional hosted applications—your legacy software running on someone else’s server, with none of the architectural benefits that genuine cloud compute delivers. Before committing to any solution marketed as cloud, engineering and procurement teams should ask several pointed questions:
- Is this cloud or hosting? Has the vendor simply lifted an existing on-premises application into a data centre and made it accessible via a browser?
- Has the application been re-architected? Does it take advantage of elastic scaling, microservices, or cloud-native storage and compute primitives?
- Does the vendor have an agile development roadmap? Cloud-native platforms should deliver continuous, value-adding enhancements—not periodic monolithic upgrades.
- What are the actual total-cost and performance characteristics? A hosted legacy application may carry the same or greater operational overhead as the on-premises original.
Cloud adoption should be driven by pragmatism and due diligence, not by a mandate to move everything off-premises for its own sake. The right question is never “Can we put this in the cloud?” but rather “Does cloud compute provide a measurable advantage for this specific workload, security model, and user need?”
Where Cloud Migration Actually Stands
The first wave of cloud migration—moving straightforward, low-risk workloads—is largely complete. Estimates at the time of this analysis placed roughly 20% of enterprise compute in public cloud environments. What remains is a harder category: workloads that are more complex, more tightly coupled to on-premises systems, or subject to stricter compliance requirements.
These harder workloads are also, paradoxically, the ones most likely to generate meaningful business value once migrated successfully. The transition represents more than a technology change—it requires new operating models, new skills, and in many cases a genuine re-evaluation of application architecture. Some workloads will ultimately prove impractical or uneconomical to migrate, and new applications continue to be provisioned on-premises where that remains the appropriate choice.
Digital Transformation ≠ Wholesale Cloud Migration
A widespread misconception equates digital transformation with moving everything to the public cloud. This conflation carries real costs. According to data cited from an Everest Group survey, 73% of enterprises failed to deliver any measurable business value from their digital transformation efforts. While causation is difficult to isolate, a likely contributor is treating technology migration as an end in itself rather than as a means to improve processes, customer experiences, or competitive positioning.
A genuine transformation starts with identifying the target business outcomes and then selecting the appropriate technical form factor—cloud, hosted, or on-premises—to achieve them. The result is often a deliberate mix of all three, each serving the workloads it is best suited for.
Digital Distress Is a Real Competitive Risk
IDC projected that by 2020 a significant proportion of organisations would be either “digitally determined” (actively using technology to drive advantage) or “digitally distressed” (falling behind because of inadequate digitisation). The intervening years have borne this out: established brand names have struggled, been acquired, or exited markets, not because technology was unaffordable but because they failed to adapt to customer expectations for seamless, omnichannel digital experiences.
The barriers to effective digitisation are no longer primarily financial or technical. The determining factors are organisational: the willingness to change, the capability to execute, and the discipline to select the right platform for each use case while avoiding vendor lock-in that constrains future options.
Why Multi-Cloud Happened by Osmosis—and Why That’s Fine
Most enterprises did not architect a multi-cloud strategy from scratch. They arrived at it incrementally, as individual application choices drove platform selections—much the way mixed UNIX, Novell NetWare, LAN Manager, Windows NT, and VM environments emerged in earlier decades, each pulled into existence by the operating system requirements of the applications running on top of them.
Today, different SaaS and PaaS vendors offer varying levels of integration with AWS, Azure, Google Cloud, and other platforms. Choosing a single public cloud provider and constraining all future application decisions to that platform is increasingly impractical. The right cloud for a given application is determined by that application’s specific performance, compliance, integration, and geographic requirements—not by a top-down mandate.
Accepting multi-cloud as the default state removes a false constraint and lets teams optimise at the workload level. It does, however, introduce real operational challenges that must be addressed deliberately:
- Compliance and data sovereignty across providers with different certification scopes and regional footprints
- Skill set breadth required to operate competently across multiple cloud control planes and toolchains
- Consistent security posture when identity, network policy, and secrets management span disparate platforms
- Observability and monitoring across heterogeneous environments without gaps or duplicated tooling
- Cost visibility and optimisation when spend is distributed across multiple billing models
What the Forrester/IBM Research Found
The Forrester survey commissioned by IBM identified the primary drivers behind enterprise multi-cloud strategies:
- Higher application and infrastructure performance
- Flexibility to match workloads to the most appropriate platform
- Improved customer experience enabled by best-in-class services
- Ability to support rapid organisational change
The same research found that 39% of IT organisations reported a loss of competitive edge rather than a gain—a signal that cloud adoption without coherent strategy, skills investment, and architectural discipline can actively harm the business. The research also reinforced a point that many finance teams resist: delaying refresh and upgrade investments is not a saving. Deferred modernisation accumulates technical debt that ultimately costs more to resolve and imposes measurable drag on business performance in the interim.
Principles for a Workable Hybrid and Multi-Cloud Strategy
Based on the patterns described in the Forrester research and broader industry experience, effective hybrid and multi-cloud strategies share several characteristics:
- Workload-first placement decisions. Evaluate each workload against the compute, security, compliance, latency, and integration requirements it actually has, then select the appropriate environment.
- Portability as a design requirement. Architect applications to avoid deep dependency on proprietary platform APIs where the cost of that dependency exceeds its benefit. Containers and Kubernetes have become a common portability layer, though they introduce their own operational complexity.
- Co-existence, not forced migration. Accept that a significant percentage of workloads will remain on-premises, and invest in the networking, identity, and management tooling that makes on-premises and cloud resources operate coherently together.
- Centralised governance, decentralised execution. Standardise on security baselines, cost tagging, and compliance controls centrally, while allowing individual teams to choose cloud services that best serve their specific applications.
- Skills investment as a first-order concern. Multi-cloud complexity compounds quickly without teams that understand the nuances of each platform. Training and hiring plans should be explicit components of any cloud strategy, not afterthoughts.
Conclusion
Hybrid and multi-cloud are not aspirational architecture patterns—they are the operational reality for most enterprises. The organisations that will gain competitive advantage are those that stop treating multi-cloud as a problem to be solved in favour of a single platform, and instead build the tooling, governance, and skills to operate heterogeneous environments well. Cloud adoption driven by genuine workload fit, with clear business outcomes attached, consistently outperforms adoption driven by the assumption that cloud is categorically better for everything.
The Forrester data is a useful reminder: technology investment without strategic clarity does not automatically translate to business value. The hard work—migrating complex workloads, upskilling teams, and building coherent multi-cloud operations—is where the real returns are found.