Initial organization alignment

The most important aspect of any cloud adoption plan is the alignment of people who will make the plan a reality. No plan is complete until you understand its people-related aspects.

True organizational alignment takes time. It will become important to establish long-term organizational alignment, especially as cloud adoption scales across the business and IT culture. Alignment is so important that an entire section has been dedicated to it in the Organize methodology of the Cloud Adoption Framework.

Full organization alignment is not a required component of the cloud adoption plan. However, some initial organization alignment is needed. This article outlines a best-practice starting point for organizational alignment. The guidance here can help complete your plan and get your teams ready for cloud adoption. When you're ready, you can use the organization alignment section to customize this guidance to fit your organization.

Initial best-practice structure

To create a balance between speed and control, we recommend that during cloud adoption, at a minimum, you have people accountable for cloud adoption and cloud governance. This might be a team of people sharing responsibilities for each of these areas, or capabilities. It might also be individual people who are both accountable for the outcomes and responsible for the work. In either scenario, cloud adoption and cloud governance are two capabilities that involve natural friction between moving quickly and reducing risks. Here's how the two teams fit together:

Cloud adoption with a cloud center of excellence

It's fairly intuitive that cloud adoption tasks require people to execute those tasks. So, few people are surprised that a cloud adoption team is a requirement. However, those who are new to the cloud may not fully appreciate the importance of a cloud governance team. This challenge often occurs early in adoption cycles. The cloud governance team provides the necessary checks and balances to ensure that cloud adoption doesn't expose the business to any new risks. When risks must be taken, this team ensures that proper processes and controls are implemented to mitigate or govern those risks.

For more information about cloud adoption, cloud governance, and other such capabilities, see the brief section on understanding required cloud capabilities.

Map people to capabilities

Assuming that the suggested structure aligns to your cloud adoption plan, the next step is to map specific people to the necessary capabilities. To do so, answer the following questions:

  • What person (or group of people) will be responsible for completing technical tasks in the cloud adoption plan?
  • What person will be accountable for the team's ability to deliver technical changes?
  • What person (or group of people) will be responsible for implementing protective governance mechanisms?
  • What person will be accountable for the defining those governance controls?
  • Are there other capabilities or people that will have accountability or responsibility within the cloud adoption plan?

After you've documented the answers to these questions, you can establish plans for skills readiness to define plans to prepare these people for forthcoming work.

Next steps

Learn how to plan for cloud adoption.