10 cloud strategy questions every IT leader must answer

It’s no longer a question of whether organizations are moving to the cloud but rather how well it’s going. Cloud isn’t that shiny new object in the distance, full of possibility. It’s come down to earth — sometimes with an unexpected thud onto the wrong side of a company’s balance sheet.

“There are so many people who bought into cloud without thinking through the real reasons why they were doing this and what they wanted to accomplish,” says David Mitchell Smith, distinguished vice president and analyst at Gartner focused on cloud computing and digital foundations. Companies may have had highly detailed migration or execution plans, but many failed to develop a point of view on the role of cloud in the enterprise.

Although some continue to leap without looking into cloud deals, the value of developing a comprehensive cloud strategy has become evident. “Today we face the harsh reality of cloud costs, if not done right,” says Jay Upchurch, executive vice president and CIO at SAS. “It’s important to understand your destination and focus on achieving that business value before you jump in.”

Without a clear cloud strategy and broad leadership support, even value-adding cloud investments may be at risk. “Cloud costs will often — and rapidly — become large line items on budgets. And the costs recur monthly or quarterly,” Upchurch says. “This makes cloud costs a target for finance teams and executives.”

There are other risks, too. In the absence of a business-aligned and supported cloud strategy, there may be conflicting goals and objectives, underwhelming perceived business value, and poor user experiences.

On the other hand, those CIOs who develop a well-thought-out cloud strategy are more likely to achieve better outcomes than those who don’t, says Smith.

And it’s never too late for CIOs to reassess their cloud strategies.

“Many organizations are due to revisit their cloud strategies, as their businesses have changed and vendor offerings have matured,” says Brian Alletto, technology director at digital services consultancy West Monroe. Following are some hard questions IT leaders should ask about their cloud strategy today.

1. Why are we really going to cloud?

The first and most important question is so seemingly obvious that many IT leaders think they’ve got it covered. “If you ask someone, they’ll often recite a list of a dozen potential benefits of cloud — lower costs, better security, greater agility, and so on,” says Smith. But that doesn’t answer the question. A cloud strategy should be built on business outcomes the organization is seeking to achieve, which may then align with some of those potential benefits.

“The reality is, the cloud has a vast array of options, and there really is no one-size-fits-all solution,” says Ben McIntyre, vice president of enterprise solutions and architectureatMerchant’s Fleet. IT leaders at the 60-year-old fleet management firm determined that cloud could support its rapid growth without the challenges of maintaining data centers. “When [we] decided to move to the cloud and cloud-enable our solutions, it was a decision that was directly aligned with the long-term growth strategy of the organization,” McIntyre says.

2. Are key stakeholders truly on board?

It’s critical that all impacted functions are aligned on the business value of moving to the cloud. Only then will they be able and willing to participate, says Upchurch.

To do this well, IT leaders should uncover the key objectives of each stakeholder, tie those objectives back to enterprise business goals, and align everyone on common goals through top-down discussions and mandates, says Mukesh Ranjan, vice president in the IT services team at Everest Group.

It’s essential to align cloud strategy with other existing technology strategies (e.g., data, security, development, architecture) as well. “Cloud computing doesn’t exist in a vacuum, and neither should your cloud strategy,” Gartner advises in its 2023 Cloud Strategy Cookbook. “Communicate and negotiate with other groups to create a successful cloud strategy.”

3. What are our cloud principles?

Cloud-first, buy-before-build, multicloud, cloud-native, lift-and-shift-as-last-resort. There are any number of principles that can guide cloud decision-making. While cloud migration will take place workload by workload, the organization should coalesce around its cloud principles to guide those ongoing decisions, says Gartner’s Smith.

4. Do we have a full inventory of our workloads?

To figure out where you’re going, you first need to know where you are. Many organizations skip this step as it can be substantial. But creating an inventory of existing workloads with key information about each one makes it much easier to make decisions on the cloud journey.

This may become its own separate project, but it’s important during cloud strategy development to define what information should be collected about each workload, says Smith. This may include who owns the workload; its dependencies on other applications; who authored it or what vendors are involved; security, governance, compliance, and data requirements; and special integration or location requirements. Importantly, you should also indicate the goal for the workload (e.g., efficiency, agility, cost savings) as well as any performance characteristics that will help determine whether it is a good candidate for cloud. Workloads with unpredictable demand such as mobile apps or websites may belong in public cloud, whereas efficient, virtualized, steady-state applications with predictable usage may not benefit from migration.

6. Are we taking advantage of cloud-native benefits?

Long is the list of “lifted and shifted” workloads that have resulted in cost overruns, emergency expense management, and performance issues. Such costly mistakes can be avoided with greater investment in cloud strategy.

The biggest value of cloud tends to result from cloud-native solutions, which exploit the scalability and variability benefits of cloud, says SAS’s Upchurch. At a previous company with a cost-effective corporate data center and infrastructure environment, Upchurch found that simply moving enterprise applications to the cloud would have decimated the budget. Instead, his team employed DevOps practices to rearchitect applications to take advantage of native cloud capabilities. The result was a cost-neutral cloud hosting solution that delivered other benefits such as a better user experience, rapid and transparent updates, and variable cloud usage patterns.

CIOs should ask themselves whether they’re taking full advantage of cloud services and features when migrating to cloud. “If the answer is no,” Upchurch says, “you may just be renting someone else’s data center.”

7. How will we balance security, agility, and usability?

Having appropriate levels of protection for each cloud workload is essential. But cloud cybersecurity is a different beast; it’s a shared responsibility. So, IT leaders should be clear about roles and responsibilities. In addition, “the landscape is evolving,” says Anuj Bhalla, president and global head for integrated cloud and delivery excellence at Tech Mahindra. “It is imperative for leaders to consistently evaluate and revise cloud security strategies and stay informed about emerging threats.”

What’s more, IT will need to juggle cybersecurity with competing priorities such as agility and functionality.

“To maintain the cloud-like experience for users, security must be embedded throughout the cloud-native software development and cloud architecture,” says Upchurch. “This eliminates the need for complex network firewall configurations which are difficult to automate, cost more, and destroy the cloud-like experience users expect.”

IT leaders may shift to security left with DevOps approaches and employ security practices such as static application security testing (SAST), dynamic application security testing (DAST), and interactive application security testing (IAST).

8. Do we have the right talent in place?

“Organizations slow the cloud transformation journey due to lack of internal cloud skills,” says Joe Nathan, associate principal for technology transformation at The Hackett Group. Cloud computing changes staffing requirements to varying degrees depending on the level and type of adoption. IT leaders may need fewer people managing servers and more people performing higher-level network engineering, systems integration, vendor management, data science, cloud security, or business analysis work.

Organizations also need nontechnical skills such as cloud financial management and cloud optimization, Nathan says. Some of this can be accomplished by upskilling willing professionals but IT leaders may also need to recruit cloud-savvy talent as well. Thus, HR should be a key partner in cloud strategy. 

“Skills are needed to properly interpret the requirements, understand the universe of potential solutions, and begin analyzing which of those are most likely to be an appropriate match given the organization’s myriad constraints,” says Randy Armknecht, managing director and leader of the global cloud advisory practice at Protiviti.

While IT leaders may lean on IT service partners for access to capabilities at scale, Armknecht has worked with multiple CIOs on building a culture of cloud learning within their IT teams, which can offer broader benefits. “The biggest benefit I’ve seen is the strength in community that forms as the database, network, server, security, and app developers view it as a common journey they can accomplish together,” Armknecht says. “Increased collaboration leads to increased speed of deployment and reduced errors. A knowledgeable and motivated team working together can achieve great things.”

CIOs should make sure they have change management expertise on board, too. “It takes a great deal of collaboration to shift to the cloud, and you need people who can really organize and orchestrate the changes,” says Merchant Fleet’s McIntyre. “Planning is critical, but really galvanizing all the people into an aligned approach is paramount.”

9. How will we measure and communicate the value of cloud?

At a minimum, IT leaders should know how to manage cloud costs. The scalability of cloud can rapidly result in cost overruns, says West Monroe’s Alletto. Some IT leaders tout the benefits of building FinOps capabilities early on to enable greater cost transparency.

But CIOs should be prepared to evolve beyond responsible cloud spend into demonstrating the business value of cloud, whether that’s new application development, rapid and frequent updates to existing cloud applications, customer or revenue growth, or some other cloud-enabled business outcome.

Quantifiable, dynamic, and outcome-oriented metrics are essential to track progress. “Value realization and maximization from cloud is a continuous process and needs a solid tracking and feedback mechanism for ongoing improvement,” says Everest Group’s Ranjan, who advises focusing on OKRs (objectives and key results) rather than traditional KPIs (key performance indicators).

At SAS, which has a large, advanced FinOps program that illustrates cloud cost savings and efficiencies, the next step will be using the platform to articulate the business value accruing from these investments.

“That will show and justify growing our efficient cloud spend,” says SAS’s Upchurch. Illustrating the full business impact of cloud can help any CIO “reduce the finance and executive reflex to reduce cloud costs which could be detrimental to functionality and value,” Upchurch says.

10. What’s our exit strategy?

One of the biggest cloud strategy mistakes is failing to have an exit plan, Gartner’s Smith says. Everyone knows they should have one, but no one wants to ask the question. “They think people won’t like the answer, which is that they’re locked in and it will be hard to move,” he adds.

A head-in-the-sand approach, however, is a bad idea. While cloud repatriation is rare, it’s important to describe existing dependencies and options if only to prepare for an unforeseen situation. In fact, some EU regulators now require that companies do this. A cloud contract may lay out SLAs and exit terms and conditions, but it’s incumbent on IT leaders to plan for how the decoupling would proceed, addressing relevant infrastructure and business issues.

It’s never too late to develop or refine a cloud strategy. In fact, having real-world experience with cloud, for better or worse, can help inform strategy development.

“You shouldn’t build a cloud strategy in an ivory tower without making mistakes and having learned from them,” says Smith.

Moreover, there are many organizations that have been on similar cloud journeys with successes, challenges, and failures that can be instructive to IT leaders. “It’s good corporate stewardship to learn from those who’ve gone before and apply [those lessons] to the go-forward strategy,” says Protivit’s Armknecht.

But IT leaders should not delay addressing these cloud strategy questions. “Everything takes time to accomplish,” Armknecht says. “And in the cloud, where cost is determined by use, the longer you’re overprovisioning resources or stuck with a broken architecture, the more the error costs.”