Theoretically, business leaders know it’s important to have strategies in place to align stakeholders, decision making, and activities with future organizational goals, but many still struggle when it comes to actually crafting those strategies. However, organizations with developed strategies are in a better position to obtain business value — especially when it comes to cloud computing.
A cloud strategy is a concise viewpoint on the role of cloud computing in your organization. It’s different from a cloud implementation plan, which offers the “how” rather than the “what” and “why” questions of a cloud strategy. It is not an attempt to solve everything nor a plan to move everything to the cloud.
Many of the top questions in cloud computing actually revolve around cloud strategy, and they’re becoming more urgent: “What is a cloud strategy and why do I need one?” or “How do we build a comprehensive cloud strategy?”
The sooner you establish a cloud strategy, the more able you’ll be able to anticipate the benefits and downsides of cloud use in your organization. Plus, it’s never too late to develop one. Here are the 10 ingredients to include in your organization’s cloud strategy cookbook.
This is your chance to communicate with senior management on the high-level direction of cloud implementations at your organization. Summarize the contents of the strategy document in a way that demonstrates value to people outside of IT. Include details such as the names and roles of those in your organization’s cloud council, or the cross-functional stakeholders who validate the strategy and drive support where needed. Though it will be the first thing people see, write the executive summary last, as it summarizes the entire effort.
Cloud Computing Baseline
This is where you will identify all terms and associated definitions that appear within the cloud strategy.
Many newer terms in cloud computing (for example, multicloud, cloud-native, or distributed cloud) are often cited as core parts of a cloud strategy, but the meanings aren’t well-established. Use existing terms, don’t reinvent them. In this section, you can also refer to an appendix that gives more detail.
What’s important is that all stakeholders agree on the definitions. The key is to eliminate confusion and use terms consistently when engaging in cloud computing conversations.
This section should map the business goals to the potential benefits of cloud computing and explain how to overcome the potential challenges. It should state why the organization is interested in the cloud initially.
Explore what the business is trying to accomplish, whether you need to align with an existing data center strategy, whether extenuating circumstances exist, and, of course, the impact of responding to uncertainties like the COVID-19 pandemic.
A discussion on services strategy is a good starting point for a brainstorming session to determine your guiding principles. Determine when to utilize cloud services from a public cloud provider versus build or maintain capabilities on-premises or elsewhere.
Distinguish between use cases for infrastructure-as-a-service (IaaS), platform-as-a-service (PaaS) and software-as-a-service (SaaS). Examine the applicability of all potential roles in cloud computing — consumer, provider and broker — and remember, it’s typically a huge effort to build cloud services.
As with most technology investments, there are financial considerations to cloud computing. It’s imperative to understand pricing model trends to meet expectations.
For example, IaaS is mostly aligned with hardware costs, so the price tends to go down slowly over time. IaaS is mainly a pay-as-you-go model and contracts are not required. Compare this with SaaS for applications, where the prevalent model is subscription-based and the price tends to go up over time.
Above all else, don’t believe the biggest myth about cloud — that you always save money by moving to it.
Principles are the most important part of an organization’s cloud strategy and should be explicitly stated. Common ones include:
Be sure to also document any vendor-oriented considerations in this section, such as positive relationships or investment in skills.
Workloads need to be inventoried to determine your current position. Basic information like name, ownership, dependencies, and security requirements for each workload must be captured.
Because there will likely be hundreds, if not thousands, of workloads to examine within the organization, the additional focus should be on the most critical workloads and those that are costing the most. Understand them thoroughly before you make big decisions about changes.
Cloud computing doesn’t exist in a vacuum, and neither should your cloud strategy. It needs to align with existing strategies, such as those for security, which requires its own section.
Security is a shared responsibility, but identifying roles and responsibilities in detail is critical to using the cloud securely. For instance, it’s not the provider’s fault if you leave your data unprotected. You must ensure that the data you put in IaaS is locked down appropriately.
Adhere to your existing security strategy or change it to accommodate the realities of cloud computing.
Often, other strategic efforts must be aligned with (including staffing, data center, architecture, and security). Staffing requirements are an important consideration in your cloud strategy. Cloud computing alters staffing requirements, depending on what level of cloud service you adopt: You’ll need a mix of skill sets to handle both administrative and higher-level tasks. Include HR as part of your cloud strategy council to ensure that staffing is properly addressed.
Although the massive movement of workloads back from a public cloud is rare, it’s vital to have an exit strategy that describes the dependencies and choices you have, just in case. In fact, several regulators, mainly in the EU and those in financial services, now mandate an exit strategy.
The “how” behind getting out of a cloud contract is important, but it’s just the beginning. Examine other issues, including:
Exit strategy and exit planning are often confused (as with the broader overall cloud strategy) . Focus your exit strategy on answering “what” and “why” questions. Cover the answers to “how” questions in a more detailed exit plan that is workload-specific.
The original article by David Smith, distinguished vice president analyst at Gartner, is here.
The views and opinions expressed in this article are those of the author and do not necessarily reflect those of CDOTrends. Image credit: iStockphoto/AlexRaths