The ITIL change management process explained
The ITIL change management process helps organizations assess, plan and execute changes to their IT environments with minimal downtime and disruption, while maintaining security and customer service quality. A key element of IT service management, ITIL change management involves predicting the potential impact of any change, identifying and mitigating risks, and ensuring any changes maintain the quality of the organization’s IT services.
There are five key stages in the ITIL change management process that any project management team should integrate with their wider change model to ensure successful change:
Stage one - Request for change
An ITIL change request, change proposal or (as it is more formally known) a request for change (RFC) is a document that contains information about the proposed change, such as its purpose, scope and potential impact. It is often compiled by an IT service manager.
Stage two - Assessment of change
Using the change request, the change manager or change agent will assess the proposal to determine resource requirements, technical feasibility and potential risks. They will also assess whether the change aligns with business priorities, organizational objectives and regulatory requirements.
See how Autodesk managed to maintain the data integrity of sales orders between two systems during its ERP transformation.
During the change assessment phase, the project management team may work with a change advisory board (CAB) to determine whether the change should be approved. In case of an emergency change (more on that later), they’re likely to work with a dedicated emergency change advisory board (ECAB).
Stage three - Change approval
Following thorough assessment, the change initiative will either be approved by decision-makers such as the CAB, or it will be rejected, perhaps with recommendations for further refinement.
Stage four - Implementation of change
Once a change request is approved, the change management team will put together an implementation plan that includes resource allocation and training requirements. They will arrange activities like testing and validation within a realistic change schedule. The change plan will also outline how effective communication and collaboration with stakeholders will be maintained throughout the change process. As the change is implemented, the change management team will be involved in change control, ensuring the project stays on track and managing any issues that may arise.
Stage five - Post implementation review
Reviewing the change after the implementation allows the project management team to ensure the change is fully embedded, and assess whether the desired outcomes have been achieved. Stakeholder feedback is an important part of this change evaluation, and can be used for continuous improvement.
Read: The Road to Go-Live Handbook for Running a Data-Driven System Migration