Optimize IT Change Management
Right-size IT change management to protect the live environment.
Onsite Workshop
Having an informal or no change management practice will lead to:
- More change-related incidents and outages.
- A lack of data compliance.
- A poor understanding of current IT configuration and cross dependencies.
- More service desk calls related to poor change rollout and communication.
Formalizing a change management practice will lead to:
- Fewer change-related incidents and outages.
- Faster change turnaround time.
- Higher rate of change success.
- Less change rework and a lower cost per change.
- Fewer service desk calls related to poorly communicated changes.
Module 1: Define Change Management
The Purpose
- Discuss the existing challenges and maturity of your change management practice.
- Build definitions of change categories and the scope of change management.
Key Benefits Achieved
- Understand the starting point and scope of change management.
- Understand the context of change request versus other requests such as service requests, projects, and operational tasks.
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Outline strengths and challenges |
|
| 1.2 | Conduct a maturity assessment |
|
| 1.3 | Build a categorization scheme |
|
| 1.4 | Build a risk assessment matrix |
|
Module 2: Establish Roles and Workflows
The Purpose
- Define roles and responsibilities for the change management team.
- Develop a standardized change management practice for approved changes, including process workflows.
Key Benefits Achieved
- Built the team to support your new change management practice.
- Develop a formalized and right-sized change management practice for each change category. This will ensure all changes follow the correct process and core activities to confirm changes are completed successfully.
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Define the change manager role |
|
| 2.2 | Outline the membership and protocol for the Change Advisory Board (CAB) |
|
| 2.3 | Build workflows for normal, emergency, and pre-approved changes |
|
Module 3: Define the RFC and Post-Implementation Activities
The Purpose
- Create a new change intake process, including a new request for change (RFC) form.
- Develop post-implementation review activities to be completed for every IT change.
Key Benefits Achieved
- Bookend your change management practice by standardizing change intake, implementation, and post-implementation activities.
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Define the RFC template |
|
| 3.2 | Determine post-implementation activities |
|
| 3.3 | Build your change calendar protocol |
|
Module 4: Measure, Manage, and Maintain
The Purpose
- Develop a plan and project roadmap for reaching your target for your change management program maturity.
- Develop a communications plan to ensure the successful adoption of the new program.
Key Benefits Achieved
- A plan and project roadmap for reaching target change management program maturity.
- A communications plan ready for implementation.
| Activities: | Outputs: | |
|---|---|---|
| 4.1 | Identify metrics and reports |
|
| 4.2 | Build a communications plan |
|
| 4.3 | Build your implementation roadmap |
|
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Book a Workshop View Blueprint