Gartner Sights Common Cloud Strategy Mistakes

November 21, 2022

Cloud Strategy Must Coexist with Other Strategic Efforts

A cloud strategy is a concise viewpoint on the role of cloud computing in the organization. However, business and IT leaders continue to make 10 common mistakes when crafting their cloud strategy, according to Gartner, Inc.

“A good cloud strategy should be a short and consumable document, consisting of 10 to 20 pages or slides,” said Marco Meinardi, Vice President Analyst at Gartner. “In addition, the business strategy should drive the cloud strategy and provide guidance to those who will implement it. It must coexist with other strategic efforts, not try to redo them.”

Marco Meinardi, Vice President Analyst at Gartner explained how to avoid making the same mistakes while developing a cloud strategy.

Business and IT leaders should collaboratively build a cloud strategy and avoid the following 10 mistakes when building their cloud strategy:

1. Assuming It’s an IT (Only) Strategy

Cloud computing isn’t only about technology. Those outside IT have skills and knowledge critical to cloud strategy success. “Business and IT leaders should avoid the mistake of devising an IT-centric strategy and then trying to “sell it” to the rest of the business,” said Meinardi. “Business and IT should be equal partners in the definition of the cloud strategy.”

2. Not Having an Exit Strategy

Devising an exit strategy from cloud providers is difficult, which is one of the reasons why many leaders don’t create one. Many organizations believe they don’t need an exit strategy because they don’t expect to bring anything back from the cloud. However, an exit strategy is vital to the success of an organization’s cloud strategy. “It’s like having an insurance policy in your drawer, that you hopefully will never need to use,” said Meinardi.

3. Combining or Confusing a Cloud Strategy with a Cloud Implementation Plan

A cloud strategy is different from a cloud implementation plan and a cloud strategy must come first. It is the decision phase in which business and IT leaders decide the role that cloud computing will play in the organization. A cloud implementation plan comes next, putting the cloud strategy into effect.

4. Believing It’s Too Late to Devise a Cloud Strategy

It is never too late to begin a cloud strategy. “If organizations drive cloud adoption without a strategy this will ultimately cause resistance from individuals who are not aligned on the strategy’s key drivers and principles,” said Meinardi. “As a result, this resistance will slow down cloud adoption and potentially jeopardize the entire cloud project.”

5. Equating a Cloud Strategy with “We’re Moving Everything to the Cloud”

Many organizations assume that having a cloud strategy implies moving everything to the cloud. “This approach deters many business and IT leaders from devising a strategy because they think it means they’ll be forced to start using cloud computing for everything,” said Meinardi. “Organizations should keep an open mind and partner with a non-cloud technology expert, such as an enterprise architect, who can bring a broad viewpoint in the definition of your cloud strategy.”

6. Saying “Our Cloud Strategy Is Our Data Center Strategy”

Many organizations confuse their cloud strategy with their data center strategy. While organizations need to keep them separate, they need to ensure they align with each other because that affects the role that cloud computing will play in their organization. “Cloud strategy decisions are workload by workload, not data center decisions,” said Meinardi.

7. Believing That an Executive Mandate Is a Strategy

Another common mistake that organizations make is to adopt cloud computing because the CEO, CIO or the head of a business unit believes that doing so will result in cost savings. Gartner analysts recommend treating executive mandates as sponsorship to devise a cloud strategy and not as a cloud strategy in and of itself. The cloud strategy should also keep the connection to the business, ensuring that organizations know why workloads are moving and what the goal is.

8. Believing That Being a <Fill in Vendor> Shop Means That Is the Cloud Strategy

Organizations will likely use several different cloud services over time. As the use of cloud services could become increasingly broad and diverse, business and IT leaders should devise a broad strategy by accommodating multiple types of scenarios, cloud services, vendors and non-cloud environments.

9. Outsourcing Development of Your Cloud Strategy

Outsourcing an organization’s cloud strategy may sound attractive, but should not be done – it is far too important to outsource. Instead, Gartner analysts recommend that business and IT leaders use third parties — even the cloud provider — for implementation. This can be a cost-effective way of procuring the scarce cloud skills their organization needs.

10. Saying “Our Strategy Is Cloud First” Is the Entire Cloud Strategy

A cloud-first approach means that if someone asks for an investment, the default place for them to build or place the new asset is in the public cloud. “But cloud-first doesn’t mean cloud only. If business and IT leaders adopt a cloud-first principle, their strategy should work out the exceptions to the default choice that will make applications and elsewhere other than in the cloud,” said Meinardi.

According to Akshay Sharma, CTO, Kovair Software, and former Gartner Analyst, “We agree with the Gartner findings, that cloud strategy must coexist with all other strategic efforts, like M&A IT, to Digital Transformation, with Innovative Service Creation, and Solutions Productization. We see a cloud-native infrastructure as critical to the success of building a strategic M&A IT Digital Transformation strategy, and virtualized core network, with Pay-as-a-you-Grow Industry4.0 Applications enablement. Newer iPaaS: integration Platform as a Service, from vendors like Kovair providing applications integration to newer Value Stream Management and Delivery will need solutions from Kovair supporting Project and Portfolio Management to define the department people, projects, tasks, workflows, etc., and with DevSecOps, or ALM all supported by IT teams doing any development on prem or to the cloud.”