AWS prescriptive-guidance documentation change
Summary
Updated organizational change management framework terminology from 'Make Culture Change Stick' to 'Make It Stick'. Enhanced content around post-implementation sustainability planning, including integration with performance metrics, training programs, and continuous monitoring. Added emphasis on embedding cloud adoption into organizational processes and long-term metric tracking.
Security assessment
Changes focus on organizational process improvements and sustainability planning without addressing security vulnerabilities, controls, or features. Content updates relate to change management frameworks and operational sustainability, with no references to security mechanisms, vulnerabilities, or incidents.
Diff
diff --git a/prescriptive-guidance/latest/strategy-ocm/make-it-stick.md b/prescriptive-guidance/latest/strategy-ocm/make-it-stick.md index 577426861..5955c4de5 100644 --- a//prescriptive-guidance/latest/strategy-ocm/make-it-stick.md +++ b//prescriptive-guidance/latest/strategy-ocm/make-it-stick.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Change Acceleration 6-Point Framework and OCM Toolkit](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Change Acceleration 6-Point Framework and Organizational Change Management Toolkit](introduction.html) @@ -9 +9 @@ -# Point 6. Make Culture Change Stick +# Point 6. Make It Stick @@ -11 +11 @@ -Make Culture Change Stick takes the work of the change acceleration framework and builds sustainability to stand and last the test of time. In this workstream, you create feedback loops for repeatable patterns and lessons learned, actively manage adoption, and create a post-implementation and sustainability plan so that the change acceleration team can be disbanded, and the changes, behaviors, and culture that has been created can be operationally and passively (rather than actively) managed. Make Culture Changes Stick has three subpoints: +Make It Stick takes the work of the change acceleration framework and builds sustainability to stand and last the test of time. In this workstream, you create feedback loops for repeatable patterns and lessons learned, actively manage adoption, and create a post-implementation and sustainability plan so that the change acceleration team can be disbanded, and the changes, behaviors, and culture that has been created can be operationally and passively (rather than actively) managed. Make it Stick has three subpoints: @@ -13 +13 @@ Make Culture Change Stick takes the work of the change acceleration framework an -6.1 Establish feedback loop + * 6.1 Establish feedback loop @@ -15 +15 @@ Make Culture Change Stick takes the work of the change acceleration framework an -6.2 Create adoption management checklist + * 6.2 Create adoption management checklist @@ -17 +17 @@ Make Culture Change Stick takes the work of the change acceleration framework an -6.3 Develop post-implementation and sustainability plan + * 6.3 Develop post-implementation and sustainability plan @@ -19 +18,0 @@ Make Culture Change Stick takes the work of the change acceleration framework an -This section provides a brief overview of Make Culture Change Stick and its subpoints. For a detailed discussion, see the guide [AWS Organizational Change Acceleration (OCA) 6-Point Framework – 6. Make Culture Change Stick](https://docs.aws.amazon.com/prescriptive-guidance/latest/oca-framework-make-culture-change-stick/). @@ -21 +20,3 @@ This section provides a brief overview of Make Culture Change Stick and its subp - + + + @@ -35 +36 @@ _When do you use it?_ -Ideally, feedback loops should be incorporated into the plan as part of measurement. In designing the feedback process, determine a reasonable timeframe for responding to inquiries or comments. Consider the timeliness of providing feedback in relation to the program’s speed and cadence. For example, feedback that is captured on a weekly, biweekly, and monthly basis can then be used as input into a scrum retrospective meeting. +Ideally, feedback loops should be incorporated into the plan as part of measurement. In designing the feedback process, determine a reasonable timeframe for responding to inquiries or comments. Consider the timeliness of providing feedback in relation to the program's speed and cadence. For example, feedback that is captured on a weekly, biweekly, and monthly basis can then be used as input into a scrum retrospective meeting. @@ -55 +56 @@ _What is it?_ -A post-implementation and sustainability plan is a document that helps an organization achieve its long-term goals, even when the dedicated cloud transformation team disbands. The objective of this plan is to enable organizations to ensure that people-related mechanisms remain in place following a cloud transformation effort. +A post-implementation and sustainability plan is the continued refinement of the sustainability plan developed in [Envision the Future](./envision-future.html). This plan is crucial for ensuring the long-term success of cloud transformation, even after the dedicated transformation team disbands. The objective is to ensure that people-related mechanisms remain in place and evolve following a cloud transformation effort, establishing enduring mechanisms to maintain and evolve cloud adoption practices and embed these into the organization's foundations. By focusing on sustainability, organizations can secure lasting returns on their cloud investments, maintain momentum in innovation and efficiency gains, adapt more readily to emerging cloud technologies and practices, and foster a culture of continuous improvement and cloud fluency. @@ -61 +62 @@ To ensure that change persists, is embedded, and is sustainable, consider the fo - * Embed the change into employee performance plans or job responsibilities. + * Integrate cloud adoption metrics into employee performance plans or job responsibilities. @@ -63 +64 @@ To ensure that change persists, is embedded, and is sustainable, consider the fo - * Dedicate a percentage of full-time employees’ time to monitor the change. + * Dedicate a percentage of full-time employees' time to monitor and drive cloud adoption. @@ -65 +66 @@ To ensure that change persists, is embedded, and is sustainable, consider the fo - * Align change-related activities with other formal processes and policies such as the annual performance plan and compliance training plans. + * Align cloud-related activities with other formal processes and policies such as the annual performance plan, compliance training plans, hiring plans, and budgeting processes. @@ -72 +73 @@ _Why is it valuable?_ -When a major step of the cloud transformation process (such as migration or modernization) is complete, additional changes are likely to emerge. Creating a long-term strategic plan to sustain those changes is essential. For example, changing the culture or behavior in one area of the organization might result in a process change in another area, or a change might have to be repeated across other business units. +When a major step of the cloud transformation process (such as migration or modernization) is complete, additional changes are likely to emerge. Creating a long-term strategic plan to sustain those changes is essential. For example, changing the culture or behavior in one area of the organization might result in a process change in another area, or cloud success might need to be scaled across other business units. Sustaining improvement gains over time requires a proactive and systematic approach for creating internal sustainability and ownership. @@ -76 +77 @@ _When do you use it?_ -Every cloud transformation involves a number of stakeholders and implementors of the change acceleration plan. It is important to identify who should be involved in the ongoing sustainability of the change project. You can then set timeframes to re-evaluate and review ongoing ownership at intervals after the official completion of the project (for example, after 3 months, 6 months, or 12 months, depending on the project duration). Depending on project requirements, you might also have to develop a continuous improvement plan or an ongoing review plan to monitor and evaluate your change. A continuous improvement plan might include: +Every cloud transformation involves a number of stakeholders and implementors of the change acceleration plan. As you complete the initial stages of cloud transformation, refine the sustainability plan to address ongoing needs and embed cloud adoption into standard operations. It is important to identify who should be involved in the ongoing sustainability of the change project. You can then set timeframes to re-evaluate and review ongoing ownership at intervals after the official completion of the project (for example, after 3 months, 6 months, or 12 months, depending on the project duration). Depending on project requirements, you might also have to develop a continuous improvement plan or an ongoing review plan to monitor and evaluate your change. A continuous improvement plan might include: @@ -90,0 +92,2 @@ Every cloud transformation involves a number of stakeholders and implementors of +Review your change planning materials and feedback to identify key risks that could be addressed with future change projects and unexpected feedback that has emerged. Prioritize potential future changes and conduct a high-level change impact assessment. Identify future change sponsors and document OCA processes and procedures for reuse. Identify OCA activities that need to be completed or should continue beyond the life of the initial cloud projects and determine what formal structures and responsibilities need to be established or assign to standard roles. + @@ -114 +117 @@ Additionally, you will need to address training gaps that were discovered after - * Documenting a remediation training plan (for example, training for new hires, quarterly or event-driven training refreshers). + * Documenting a future state training plan (for example, training for new hires, quarterly or event-driven training refreshers, training on new AWS solutions and services, AWS certification and re-certification plans). @@ -123 +126,5 @@ Additionally, you will need to address training gaps that were discovered after -When you include these activities as part of your sustainability plan, your organization will gain a better understanding of how well change is persisting within the organization. Being patient, persistent, data-driven, and methodical will help your organization adhere to the sustainability plan. +An important factor in sustaining change and cloud adoption is the ongoing collection and monitoring of key metrics. Identify the key metrics at multiple organizational levels that are indicative of achieving the planned business outcomes. For each level of metrics (organizational change acceleration, cloud program and workstream, and business outcomes), ensure that a data collection and measurement plan, plan for automation, responsible, accountable, consulted, informed (RACI) matrix, and response plan are in place to ensure sustainability. + +Determine who needs to approve the completion of change acceleration activities. Organize meetings with the change sponsor and business leaders to discuss any new change projects, transition of ongoing ownership, outstanding items, and approval of project deliverables. + +When you include these activities as part of your sustainability plan, your organization will gain a better understanding of how well change is persisting within the organization. Being patient, persistent, data-driven, and methodical will help your organization adhere to the sustainability plan and ensure that cloud investments continue to yield benefits well into the future. @@ -133 +140 @@ Point 5. Enable Capacity -Wrap Up +Wrap up