Cloud adoption antipatterns

Customers often experience cloud adoption antipatterns. These missteps commonly occur in design, planning, or implementation when migrating to the cloud. Antipatterns can block innovation and prevent businesses from adopting and realizing goals.

The following table lists antipatterns and the methodologies, or cloud adoption phases, that these patterns occur in. The linked articles provide examples of each antipattern and solutions.

Methodology Antipattern Reference
Strategy Inadequate motivation Antipattern: Adopt the cloud without establishing goals
Strategy Misaligned motivation Antipattern: Fail to communicate motivations
Plan Wrong cloud operating model Antipattern: Choose the wrong cloud operating model
Plan Wrong service model Antipattern: Choose the wrong service model
Plan Replacement instead of modernization Antipattern: Replace architecture
Ready Preview services in production Antipattern: Assume released services are ready for production
Ready Inaccurate resiliency and availability assumptions Antipattern: Assume increased resiliency and availability
Ready IT as cloud provider Antipattern: Become a cloud provider
Manage Neglect of business outcomes Antipattern: Focus on tooling, not business outcomes
Govern Misaligned shared responsibilities Antipattern: Misunderstand shared responsibilities
Govern Inaccurate out-of-the-box security assumptions Antipattern: Assume out-of-the-box solutions provide security
Govern Custom compliance or governance frameworks Antipattern: Use a custom compliance or governance framework
Organize IT cost centers Antipattern: Treat IT as a cost center
Organize Platform development without business approval Antipattern: Invest in new technology without involving the business
Organize Core business function outsourcing Antipattern: Outsource core business functions
Organize Technical decision makers instead of cloud engineers Antipattern: Hire technical decision makers instead of developing cloud engineers

Next steps