Planning your multicloud digital transformation: The key questions

Planning your multicloud digital transformation: The key questions - Blog

Every one of your clients takes it for granted that their digital, multicloud transformation will lead to new opportunities.

And, of course. all while mitigating any possible risks too.

In which case, it’s essential to have a Cloud Entry Framework (CEF), a strategic process defining how to adopt cloud resources and select which workloads are moved there.

Naturally, each CEF is unique to each client.

So how do you go about creating the ideal CEF for each client?

 

The poor state of necessary planning

A carefully considered CEF ensures the appropriate development of data management and governance across private and public clouds, while linking together various ‘as-a-service’ options.

And yet less than 6% of respondents to the survey admitted to having a framework in place.

The majority of businesses have been simply adding cloud capabilities to meet moment-to-moment demands. Burdening themselves with a platform no one specifically asked for and no one intended on using.

 

Naturally, the CEF that’s just right for an enterprise must be tailored to an enterprise’s own particular circumstances

That means every one of these essential points must not only be considered but also acted upon:

  • Implement, maintain, upgrade, and retire the entire (not just cloud) technology stack
  • Maintain quality of service while scaling the platform to include emerging technologies
  • Migrate to the platform applications that have been adapted to new technologies
  • Ensure the visibility and control of any compliances and services adopted by employees, such as security and cost concerns

 

Five Essential Questions

These are the key questions that absolutely must be asked to ensure a smooth and seamless adoption of cloud capabilities.

1] Which workloads should move?

Some workloads will be priority candidates to move to cloud.

Which ones?

There’s such a wide variety of workloads that it might not be immediately obvious.

Yet generally, it makes sound sense to leave until last (if they’re actually going to be moved at all!) the more regulated or sensitive data workloads.

While the best place to start usually involves development or test environments, along with the more obviously necessary projects created for recognisably specific purposes.

 

2] Where should the workloads be moved to?

Some clouds are more appealing than others.

Why?

Strong integration with other technologies and their providers is a prime factor.

A lack of hidden data transfer fees is also important.

As is any assumption on the security or compliance risk liabilities that can be made.

And just what do you know of the cloud provider’s history?

In short, you need to make a reliable assessment of the physical location, capabilities, and technology and support offerings of each cloud you’re planning on using.

 

3] When do these workloads move, if at all?

Covering infrastructure shortfalls by adding resources as and when needed is equivalent to relying on sticky plasters rather than conducting the required operation.

You need time to focus on ensuring required integration across all platforms.

Then, when you’re moving a workload, you’re also embarking on a purposeful shift that’s actually augmenting cloud capabilities as part of in an improved, more controllable structure.

 

4] How should these workloads be handled?

0ne approach amongst many for migrating your applications to the cloud is ‘Lift and Shift.’

It’s a relatively easy way to move a workload and its associated data to a cloud platform, as it doesn’t involve redesigning the application.

But what’s the point in moving workloads if you’re not also taking the opportunity to leverage new efficiencies and technologies?

As part of a more holistic plan for digital transformation, this is an ideal time to take a more ‘Transform and Shift’ approach.

Identify exactly where your most important processes are currently taking place.

Then redesign, document, and automate these processes, taking into account knowledge transfer, employee training, and risk assessment and mitigation.

 

5] What special considerations exist for different workloads?

When asked to nominate the key service provider characteristics, 65% of the ISG survey respondents indicated that cloud expertise and talent were of particular importance to them.

This, of course, is because workloads can vary considerably.

The best advice on open-source, technology, and interoperability will always come from providers familiar with a wide variety of data management and governance technology.

They will generally know, too, if certain types of workloads or datasets need to be located in a particular country’s datacentre.

 

The CEF: the digital backbone of any transformation

An enterprise’s cloud infrastructure needs to be assessed and added to in a deliberate, strategic way.

Only in this way can they be sure of planning and building a robust digital backbone, drawing one step closer to a comprehensive digital transformation.

Are you ready to provide your clients with a carefully considered CEF?

Read the full report above.

Then discover the only hybrid multicloud offering full control, along with how to optimise applications and workloads from on prem to the edge.

 

Related content

Resource Centre

IBM Hybrid Multicloud: Optimise applications and workloads anywhere

Resource Centre

Extracting more business value from data for you and your clients

Blog

Facing fresh challenges: Together we shall endure

Back to top