4.1 Change acceleration implementation - AWS Prescriptive Guidance

4.1 Change acceleration implementation

Overview

The objective of this activity is to launch the activities set forth in the change strategy and plan (see Envision the Future, 3.1). A change strategy and plan provide a thoughtful, structured, programmatic approach to delivering the right change tactics to the right people at the right time throughout the course of the cloud transformation. They outline a comprehensive approach to ensure that changes introduced to the organization as a result of the cloud are accepted by leaders, employees, and other stakeholders with minimal disruption and maximum results. They provide a systematic mechanism for adjusting the application of tools, technologies, processes, or skills during a project or initiative. They describe the specific ways in which the organization will address changes in the way it operates its business, technology, supply chain, organizational structure, or project scope. The change strategy provides direction and results in informed decision-making throughout the cloud transformation process.

In the change acceleration implementation activity, the focus of the OCA team is to work closely with all cloud workstreams and stakeholders to implement the elements of that strategy and plan in a programmatic, rhythmic timeline that lasts the life of the program, and accelerates and decelerates with the various milestones over time.

Change can be highly disruptive to an organization and will affect both the cloud transformation and the surrounding environment over time. For example, new leaders might emerge or join, and others might retire or leave. New business transactions such as mergers, acquisitions, and divestitures might take place that cause the cloud transformation to accelerate, pause, or change scope.

The following diagram illustrates how OCA can minimize the gap in perception and productivity during change acceleration.

Minimizing gaps in perception and productivity through OCA.

Best practices

Key best practices for the implementation of change acceleration include the following:

  • For each major milestone, describe how the changes will impact the organization and who will be affected. These changes might include data center exits, deployments of new solutions and features, and establishing a Cloud Center of Excellence (CCOE).

  • Create a plan for stakeholders to recognize when a change is needed, and how to mitigate impacts to their workforce.

  • Follow the defined process or mechanism for implementing, approving, and monitoring changes to make sure that they have the desired effect.

  • Regularly review and update both the strategic vision and business case for cloud transformation. This ensures that messaging remains consistent, relevant, and aligned with changing business conditions.

  • Interview key leaders who join the organization, and identify impacted stakeholders for all key milestones early in the planning process. Periodically assess their alignment throughout the life of the program.

  • Continuously integrate partners who join the broader cloud transformation program team to ensure consistent objectives and key results (OKRs), timelines, and motivations.

  • Continuously partner with enabling functions that can prove helpful when they are engaged, and can cause timing and budgetary delays when they're not engaged. For example, these functions might include human resources, training, finance, cross-functional leaders, line of business leaders, and other partners or vendors who are directly or indirectly impacted. Plan to speak to these stakeholders at least quarterly. At the minimum, provide a program update and show them that you value their input. A few action items or insights will typically result that might derail plans if they aren't proactively addressed.

Change acceleration checklist

Creating a change acceleration checklist of activities can be helpful to see if your change strategy and plan (and associated user stories) are comprehensive and robust. The following table provides a list to get you started.

Area

OCA 6-Point Framework reference

Actions

Project management

Engage the Organization, 1.5 Program goals and objectives

  • Ensure close integration and participation in weekly meetings for the cloud transformation project (for example, sprint ceremonies, backlog planning meetings, and launch readiness planning sessions).

  • Update the risk management and mitigation log for change acceleration risks every week.

  • Update the change acceleration reporting scorecard and status reports every week (or for each sprint).

Leadership alignment and stakeholder analysis

Align Leaders, 2.1 IT and business leader alignment

Align Leaders, 2.2 Stakeholder assessment

  • Prepare the stakeholder analysis approach.

  • Identify leaders to interview.

  • Conduct stakeholder interviews and analysis activities.

  • Present findings to the leadership team.

  • Insert risk findings into the risk management and mitigation log.

  • Update and maintain the stakeholder matrix.

  • Use the stakeholder matrix as an input to persona-based change impacts, communications, and training.

Change impact assessment

Align Leaders, 2.3 Change impact assessment

  • Assess change impacts and document them.

  • Determine the appropriate interventions to manage and mitigate impacts to user groups, timelines, data center exits, product launches, and other important milestones.

Risk management and mitigation

Envision the Future, 3.5 Risk mitigation strategy and plan

Engage the Organization, 4.5 Risk mitigation implementation

  • Prepare the change risk assessment approach.

  • Conduct risk assessment activities such as  interviews, focus groups, and surveys.

  • Analyze and present findings to the leadership team.

  • Assign and mitigate risks and issues according to risk management guidelines.

  • Update the change acceleration plan and stakeholder engagement plans as needed.

Sponsor roadmap

Envision the Future, 3.6 Sponsor roadmap

  • Prepare the sponsor approach.

  • Prepare the materials for sponsors, such as key messages, FAQ, timelines, and roadshow presentations, according to the leadership action plan.

  • Identify sponsors and leaders.

  • Engage and onboard sponsors and leaders.

  • Monitor and measure the progress of leadership action plan activities according to the sponsor roadmap.

  • Support sponsors and leaders as needed. Update materials and FAQ as needed.

Change acceleration plan

Envision the Future, 3.1 Change strategy and plan

  • Continuously monitor and measure the implementation of the change plan.

Additional steps

To get started on change acceleration implementation, do the following:

  1. Review the change strategy and plan in its entirety at key milestones, such as data center exits, migrations, new solutions, business transactions (mergers, acquisitions, divestitures), leadership changes, and at a minimum once per quarter.

  2. Participate in all weekly status meetings and sprint ceremonies as part of the cloud transformation integrated team.

  3. Meet with stakeholders regularly as part of their leadership action plans, and update key messages, FAQ, and communications as required, to stay relevant with the current IT and business strategy.

  4. Manage people-related, cultural, organizational, and political risks by using the risk management and mitigation log. Be careful to document highly sensitive issues separately and share them only with a limited  audience on a need-to-know basis.

  5. Review and update the cloud business case as required, and create new change acceleration activities as necessary to realize the ROI of the cloud.

  6. Document and share lessons learned with the cloud transformation team and other teams within the company to create a culture of evolution, iteration, and continuous improvement.

The effective implementation of change acceleration is critical for realizing the full value of cloud transformation. By following these steps and best practices, and systematically implementing the change strategy, organizations can minimize disruption, align stakeholders, and accelerate cloud adoption to achieve their desired business outcomes.