Posts

Cloud Adoption Missteps Part 3: Governance and Organization

Common_Cloud_Adoption_Missteps_PT3_2-1 Cloud Adoption Missteps Part 3: Governance and Organization

Welcome back to the final part of our 3-part Cloud Adoption Missteps series where we will be going over some of the errors and mistakes that take place during the governance and organization stages of the Cloud Adoption Framework for Azure. The first two parts of the series gave insight into earlier steps in the framework process, what they entail, and common cloud adoption missteps that can arise. To read an overview of what the Cloud Adoption Framework for Azure is and some of the antipatterns that take place during the first 2 stages of the framework, click here. If you would like to check out the second part of the series, “Common Cloud Adoption Missteps Part 2: Adoption and Management Stages”, you can read it here.

The conclusion of the Cloud Adoption Missteps series will cover antipatterns in the governance and organization stages. We will share what goes on during these steps, common antipatterns, and some strategies to mitigate the antipatterns that may arise. 

Governance Stage

Taking organizations to the cloud is a complex yet highly rewarding process as we’ve clearly outlined in the past. However, it’s important to note that constant cloud governance must take place to create a strong cloud governance foundation. To learn some of the governance methodologies for the cloud, read this guide from Microsoft.

There are 3 main antipatterns that take place during this stage in the Cloud Adoption Framework: misunderstanding responsibility, straying too far from the compliance framework requirements, and using custom compliance.

Misaligned Shared Responsibilities

Though the Cloud Adoption Framework for Azure is well-defined and clearly laid out, it can still be difficult to recognize where your organization’s responsibilities end and your cloud service provider’s (CSP) begins. Oftentimes that line gets blurred and that’s when the problems begin. Whether it’s security concerns or non-compliant servers, it’s important to address those issues right away. 

By building a “readiness plan”, you and your CSP can find that middle ground that works for everyone. A readiness plan focuses on capturing concerns, identifying gaps, and partnering with other teams to overcome this hurdle. For a more detailed look into what a readiness plan entails, check out Microsoft’s guide here.

Inaccurate Security Assumptions

It’s easy to assume that the move to the cloud is automatically a security upgrade, and that’s not necessarily wrong; however, it’s not a great idea to assume that out-of-the-box solutions provide security. Focusing on adhering to the compliance standards for Azure and using Azure portal ensures more stable security. Learn more about the Azure Security Centre here.

Custom Compliance or Governance Frameworks

The third and final antipattern that takes place during the governance stage is the use of a custom compliance or governance framework. Integrating these custom frameworks is very time consuming, especially when translating them to cloud settings. This will significantly slow down the cloud adoption process. Instead, rely on existing frameworks while making that transition to the cloud. It allows for ease, simplicity, and measurability of security settings. After making that transition is a good time to look at custom frameworks.

 

Organization Stage

The final stage in the Azure Cloud Adoption Framework is the organization stage. It looks at managing and organizing people (teams), structure, and the roles each person plays. Oftentimes, customers face cloud adoption missteps during the organizational stage due to a variety of aspects. The antipatterns that we will cover are 4 of the biggest missteps that often take place: utilizing IT as a cost centre, platform developing without approval, outsourcing core business functions, and hiring technical decision makers rather than cloud engineers. For more information on the organization stage in the cloud adoption framework, check out this overview by Microsoft.

Treating IT as a Cost Centre

When organizations or employees start to see IT as a cost centre rather than an enabler, pushing growth and success, there is reduced motivation in the long run. IT feels discouraged and along with that, management feels as though IT is slow and inefficient. 

Rather than viewing IT as a cost centre, try and see it as an enabler. By viewing IT as an agent with operating expenses, transparency, accountability, and optimization as are all maximized.

Investing in New Technology Without Involving the Business

Different departments all have separate functions to focus on. So it’s easy to forget that there are other business units that could be affected by even the smallest decisions. For example, if IT fails to consider business units while making design and structural decisions, it can lead to platforms that aren’t optimized or properly functioning for the business units. This leads to frustration and poor/ineffective adoption of the new platforms.

Instead, involve business units in the decision-making process. This eliminates the risk that those teams will not be able to implement or adopt new platforms. It takes into account the preferences and needs of the business units and creates a more cohesive platform that works for everyone. 

Outsourcing Core Business Functions

When running an organization, it’s easy to get caught up in outsourcing business functions to managed service providers (MSPs) and consulting partners. These partnerships can give way to a lot of exciting possibilities. However, it’s crucial to make sure that your company doesn’t become dependent on providers.

Keep critical design areas within your company, regarding subjects like risk, compliance, identity, and government. This ensures that your organization won’t become dependent on external providers, and instead will use them to speed up other important business processes.

Hiring Technical Decision Makers

Finally, the last cloud adoption misstep that we are focusing on in this series is the choice between hiring technical decision makers (TDMs) versus investing in cloud adoption engineers. TDMs are often a great way to get your cloud adoption framework up and running. However, a successful cloud adoption journey needs people with deep technical knowledge such as cloud engineers. 

Because cloud engineers are crucial for creating successful landing zones and cloud automations, they can help you realize the true potential of cloud adoption and the benefits that it brings. TDMs can always be brought in for decision-making later in the process, but cloud engineers are the ones with rich engineering knowledge.  

Conclusion

This article was the final part of a three-part series focusing on common cloud adoption missteps while using the Azure Cloud Adoption Framework. We hope that you gained a detailed overview of the many stages of the cloud adoption process and what they entail. As well as this, we hope that you are now aware of the antipatterns and cloud adoption missteps that can be easily remedied. 

Many organizations find it beneficial to work with a Cloud Solution Provider (CSP) when undergoing cloud adoption. Read our article on the benefits of using a CSP.

If you’re interested in having Optimus as your CSP, you can reach us at: info@optimusinfo.com

 

/by

Common Cloud Adoption Missteps Part 2: Adoption and Management Stages

Common_Cloud_Adoption_Missteps_PT2_2 Common Cloud Adoption Missteps Part 2: Adoption and Management Stages

Welcome back to the Cloud Adoption Missteps series, for part two: focusing on the adoption and management stages. If you haven’t already checked out our first blog post in the series for the Planning and Strategy Phases, check it out here. It covers all the easily remedied errors that one can make when following the Cloud Adoption Framework for Azure in the Adoption and Management Stages, and how to avoid them. 

In this article, we’ll be focussing on a different part of the cloud adoption framework timeline, the adoption and management stages. We’ll go over the antipatterns during both of these situations and how the cloud adoption missteps can be avoided. For more detailed information on what the Cloud Adoption Framework for Azure entails and why antipatterns are blockers for success, please refer to the aforementioned article linked above.

Common Cloud Adoption Missteps During the Adoption Stage:

The adoption stage of the Cloud Adoption Framework focuses primarily on cloud migration and what it means. Cloud migrations are the different approaches through which workloads can be moved to the cloud. For more details on cloud migration for workloads, you can check out Microsoft’s Azure Migration Guide Overview. There are four antipatterns that can occur during the Adoption Stage that we will be discussing: a lack of guardrails, a lack of assessments, forced architecture, and the use of a single subscription. 

Trying to Innovate Without Guardrails

When organizations are first trying to migrate their workloads to the cloud, it can be seemingly simple. It often feels as though there’s a lot of flexibility, which is great. But the majority of the time, when those workloads need to have increased productivity or need to store data, progress will drastically slow. This is where the idea of implementing security and compliance guardrails is highly effective. Guardrails ensure that workloads follow security and compliance regulations. Checking the guardrails with IT is an important step, especially for hybrid workloads. For more information on Azure’s “landing zones” for guardrails, click here.

Attempting to Migrate Without Extensive Assessments 

In order to plan accurately for a migration or modernization project, there are many factors that need to be taken into consideration. Without thorough planning, organizations risk creating a lot of unexpected downtime or missed potential due to not thinking the architecture or other aspects through. 

There are a few ways to get around this antipattern. For larger-scale projects, it’s crucial to undergo a thorough infrastructure assessment before the migration process begins. Modernization projects require the identification of coding antipatterns and technical debts. On the other hand, for innovation-based projects, check out this Azure guide for innovative solutions here. Finally, for large projects or workloads that need architecture change, it may be a good idea to undergo an architectural design session.

Using a “One Size Fits All” Approach to Architecture 

On the topic of architecture, one of the easiest mistakes to make is dictating your architecture. Assuming that one architecture approach will fit all of your workloads is a grave error. Instead of fixating on one architectural style, for example a microservice architecture approach, undergo an extensive assessment so your decisions can be rooted in data. Choosing an architectural approach just because other organizations are using it and it’s successful for them, doesn’t guarantee favourable outcomes for your own projects. 

Trying to Migrate with One Subscription 

Finally, trying to utilize only one subscription for all of your organization’s workloads leads to problematically designed landscapes. Then your organization is at risk for running into subscription limits, which would require time-consuming architecture adjustments. The solution is to use segmentation. Separating different tasks for various environments minimizes the chances of hitting subscription limits. Using a segmentation strategy in this situation is key; this article from Microsoft outlines what that could look like. Check it out here.

Common Cloud Adoption Missteps During the Management Stage:

We now move on to the next step of the Cloud Adoption Framework: the management stage. As aforementioned, yes, it is crucial to take care of cloud adoption and remedy those antipatterns, but it is just as important to maintain the operation of your digital assets in order to ensure smooth sailing. Not having a plan to follow in terms of managing cloud solutions, all that progress can slowly fade. There is one main antipattern during the management stage: fixating on IT tool chains.

Neglect of Business Outcomes 

It is so easy to get caught up in the ease that modern IT tools create, and the relief that it gives to team members by taking care of small tiresome tasks. And while it is beneficial to take advantage of the positives that new IT tooling has, it’s also important to measure exactly how much each tool chain is helping. The way to do this is by ensuring that your technology and business goals align. By having leaders from each of these areas come together and unanimously create business/technology goals, it’s much more clear as to whether those expectations are being met. Measuring success through business outcomes means that your organization is constantly focused on increased growth.

What’s Next?

This article was the second part of a four-part series focusing on common cloud adoption missteps while using the Cloud Adoption Framework for Azure. Stay tuned for our next article which focuses on cloud adoption antipatterns for the next stage of the framework.

Many organizations find it beneficial to work with a Cloud Solution Provider (CSP) when undergoing cloud adoption. Read our article on the benefits of using a CSP.

If you’re interested in having Optimus as your CSP, you can reach us at: info@optimusinfo.com

/by

Common Cloud Adoption Missteps during the Strategy and Planning Phase

Common_Cloud_Adoption_Missteps_2-1 Common Cloud Adoption Missteps during the Strategy and Planning Phase

 

There are many roadblocks along your journey to digital transformation. Following the guidance from the Cloud Adoption Framework closely is essential when undergoing your cloud migration.  While the Cloud Adoption Framework helps make cloud adoption easier, there are still several missteps that can lead you astray. In this article, we’ll briefly review the Cloud Adoption Framework, the main missteps made during the strategy and planning phases, and we’ll also provide some quick remedies to easily avoid these mistakes. 

 

A Review of The Cloud Adoption Framework

Microsoft’s Cloud Adoption Framework for Azure was developed as the One Microsoft cloud adoption approach. It consolidates advice and guidelines from Microsoft professionals and customers throughout the industry into one best practices guide. It shares the full lifecycle framework with detailed tips and information. If you want to learn more about the Cloud Adoption Framework, check out our previous article on the topic here.

In this article, we’ll be going over cloud adoption antipatterns. Antipatterns are missteps that occur during the cloud adoption process, usually in the design, planning, or implementation stages. They are often blockers that prevent organizations from reaching goals and achieving innovation. Next, we’ll cover common cloud adoption missteps that occur in the planning and strategy phases and how to avoid them. 

caf-diagram Common Cloud Adoption Missteps during the Strategy and Planning Phase

Cloud Adoption Framework diagram provided by Microsoft.

Common Cloud Adoption Missteps During the Strategy Phase

The strategy phase of the Cloud Adoption Framework looks at documenting business strategies and outcomes from your organization so that key stakeholders and your team members have a clearer picture of what’s going on. Two main antipatterns can take place during this stage of cloud adoption: inadequate motivation and misaligned motivation.

Inadequate Motivation

When an organization adopts the cloud without clear or well-defined goals in mind beforehand, many issues often follow. It’s hard to measure project performance without predetermined indicators of success. If a company announces cloud-led strategies without thinking through what that actually entails, it doesn’t truly give them the benefits of cloud adoption.

Organizations can avoid this simple mistake by defining their goals and KPIs before embarking on their cloud adoption journey. In doing this, measures of success become more clear and project success also becomes replicable.

Misaligned Motivation

Sometimes cloud adoption plans can fail when motivations are misaligned or not properly communicated within a company. For example, if a business sees a benefit in a specific cloud adoption strategy but does not share that with the rest of the organization, other departments have a more difficult time onboarding these strategies and implementing them.

This issue can be mitigated by clearly outlining and sharing reasons for specific cloud adoption strategies with the entire company. It creates a cohesive environment within the organization that allows for those strategies to be built upon successfully and with ease. 

Common Cloud Adoption Missteps During the Planning Phase

The planning phase of the Cloud Adoption Framework looks at taking the goals formulated during the strategy phase and turning them into a tangible plan. This cloud adoption plan can then guide teams to stick to the strategies they came up with previously, as well as helps to prioritize cloud adoption motivations. There are three main antipatterns that often take place during this stage: wrong operating model, wrong service model, and replacement instead of modernization.

Wrong Operating Model

In choosing the wrong operating model issues such as misunderstandings, extra pressures on the IT department, and more can ensue. This is due in part to the fact that the operating model is not lining up with the company’s priorities and goals as defined in the strategy stage. 

One way to mitigate this issue is by comparing models with your current operating plan before switching over. By analyzing the pros and cons of each model and weighing the benefits, it will be much easier to find the right fit. To learn more about comparing cloud operation models, read this guide from Microsoft.

Wrong Service Model

It’s important to properly look at and understand the differences between a PaaS and IaaS service model. Some may assume that a PaaS service model is more cost-efficient but that’s not always the case, and making this assumption can sometimes lead to product delivery delays, unexpected cost increases, and more. 

The best way to avoid this issue is to minimize disruption to your business at the beginning of the cloud adoption process. Using IaaS and gradually adopting a PaaS model will allow for less disruption and will also give your team some time to gain cloud adoption skills.

Replacement Instead of Modernization

Replacing large and complex products or application environments is a decision that shouldn’t be made lightly. Yes, it’s true that working in old, complex architecture landscapes is far from ideal and can lead to delays and issues. But completely replacing these systems is often very costly and involves many risks. 

Instead, looking at modernization as an option is a better alternative. Small, persistent changes to your systems can often have a bigger and safer impact than completely switching your software. As well as this, it’s often quicker and usually much cost-efficient. 

 

What’s Next?

This blog article is the first of a four-part series focussing on common cloud adoption missteps. Follow along with us to learn about some common errors in the next stages of the cloud adoption framework. 

 

 

Many organizations find it beneficial to work with a Cloud Solution Provider (CSP) when undergoing cloud adoption. Read our article on the benefits of using a CSP here. 

If you’re interested in having Optimus as your CSP, you can reach us at this email: info@optimusinfo.com

/by

Digital Transformation in a Nutshell: Understanding Microsoft’s Cloud Adoption Framework for Azure

Digital-Transformation-Clooud-Adoption-300x188 Digital Transformation in a Nutshell: Understanding Microsoft’s Cloud Adoption Framework for Azure

What is digital transformation? We’re hearing a lot about it these days, and especially more in the seemingly strange “apocalyptic” era that’s taking place right now. There has never been a time in history that there has been such a need for the Cloud. As we navigate through this uncharted territory and wonder how on earth people managed to live with so much uncertainty in the past, most of us have found solace in virtual connection. Now don’t get us wrong, we encourage and embrace the outdoors and passions that don’t require a screen in front of our eyes; however, right now, the only way to connect with those outside our household is virtually. We are all gravitating towards supporting people and programs that allow us to do that. 

So how is it that some businesses are now elevated among the rest? It’s simple. Digital transformation. Those who have taken their passions and programs to the Cloud, and done so successfully, are experiencing lower levels of strain at this time. But how can you or your business embrace digital transformation? We’re here to tell you about Microsoft’s Cloud Adoption Framework for Azure, and how it urges you to look at business objectives before jumping right into your transformation. This framework is crucial in adopting the Cloud successfully. 

What is the Cloud Adoption Framework?

It was developed by Microsoft as the One Microsoft approach to Cloud adoption in Azure. Sharing guidelines from Microsoft professionals and customers across the board, this framework aims to educate on the best practices to drive desired business outcomes. It uses a cloud adoption lifecycle, providing the full lifecycle framework with detailed steps and tips along the way. Put simply? Your ticket to digital transformation, outlined by the best in the game, packaged up and wrapped in a bow. 

Why is it Crucial for the Successful Adoption of Cloud?

A lot of people want quick results on projects without really delving into the process and examining why they’re doing what they are doing. We strongly believe that this framework should be a crucial part of your process going forward. Sure, it might be “easier” to skip the “why” questions and favour how you will move to the Cloud… but this framework makes you look at what business goals you are intent on achieving and aids in creating a plan. This is an integral part of long term success when adopting the Cloud. Microsoft defines cloud adoption as “[…] a means to an end. Successful cloud adoption starts well before a cloud platform vendor is selected. It begins when business and IT decision makers realize that the cloud can accelerate a specific business transformation objective. The Cloud Adoption Framework can help them align strategies for business, culture, and technical change to achieve their desired business outcomes.” 

We at Optimus use the Cloud Adoption Framework in our own work extensively. While planning with clients, we adopt this framework to move them to Azure because it encourages best practices and makes our clients’ cloud adoption successful. 

How to Get Started

Is your team new to this framework? An easy way to get going is to read “Get started with the Cloud Adoption Framework”, an article by Microsoft explaining how to begin your Cloud migration journey with Azure. It will walk you through the entire process while outlining best practices. From outlining how to look at your “motivations” or goals, to defining methodology, this guide has you covered on all bases. 

Find out how to implement Microsoft Azure in your business by contacting us at Optimus. Don’t miss out on the chance to take your business to the Cloud.

 

 

 

/by

Events

Nothing Found

Sorry, no posts matched your criteria

Portfolio Items