Headline: From Request to Review — The Seven Stages of ITIL Change Enablement
The Change Enablement Lifecycle
ITIL change enablement follows a structured lifecycle designed to maximize successful changes while managing risk.
Stage 1: Request & Evaluation
A change request is submitted and evaluated for necessity and impact.
Key activities:
- Submit Request for Change (RFC)
- Determine if the change is necessary
- Identify the change type (Standard, Normal, Emergency)
- Initial assessment of impact
Stage 2: Risk Assessment
Potential risks are identified and evaluated.
Key activities:
- Identify potential risks
- Assess likelihood and impact
- Determine risk mitigation strategies
- Evaluate change against business priorities
Stage 3: Approval
The appropriate Change Authority reviews and approves the change.
Key activities:
- CAB review (for Normal changes)
- Change Manager approval (for Standard changes)
- ECAB approval (for Emergency changes)
- Documentation of approval decisions
Stage 4: Implementation
The change is executed with minimal disruption.
Key activities:
- Execute change according to plan
- Follow change implementation procedures
- Coordinate with stakeholders
- Monitor for issues
Stage 5: Testing
The change is verified in a controlled environment.
Key activities:
- Test in staging or test environment
- Validate that the change works as expected
- Verify no negative impacts
- Document test results
Stage 6: Review
The outcomes of the change are evaluated.
Key activities:
- Post-implementation review
- Determine if the change achieved its objectives
- Identify lessons learned
- Document findings
Stage 7: Documentation
All changes are recorded for traceability.
Key activities:
- Update the change schedule
- Document the change outcome
- Update knowledge management
- Close the change request
The Continuous Improvement Loop
ITIL's philosophy of continuous improvement applies to change management as well. The mantra: "Great organizations live and breathe the Continuous Improvement mantra and how to navigate the complexities of change management challenges" .
Key to this is the Continuous Improvement Register (CIR): Everyone in IT should enter their ideas into the CIR, no matter how bold or small the suggestion. Continuous Improvement managers review suggestions, analyze the best ones, and create change requests for promising improvements .
Conclusion
The change management lifecycle provides a structured approach to managing changes from request to review. By following each stage, organizations can ensure changes are implemented successfully while minimizing risk.
Action Items for Your Organization
- Map your current change process against the lifecycle
- Identify gaps in your process
- Document the workflow in your ITSM platform
- Train your team on each stage
- Implement a Continuous Improvement Register
