Change Enablement
Definition
"Maximizing the number of successful service and product changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule."
To fulfill this purpose, organizations must:
- Ensure timely and effective change realization
- Minimize negative impacts from changes
- Ensure stakeholder satisfaction
- Meet governance and compliance requirements
Key Philosophy: The practice is termed "change enablement" rather than "change management" to emphasize facilitating safer changes rather than creating bureaucratic obstacles.
What is a Change?
A change represents "the addition, modification, or removal of anything that could have a direct or indirect effect on products and services."
Change Types
| Type | Risk | Authorization | Description |
|---|---|---|---|
| Standard change | Low | Pre-authorized | Well understood, fully documented, implementable without additional authorization |
| Normal change | Unknown/medium/high | Required | Requires additional authorization for planning and control |
| Emergency change | Varies | Expedited | Must be introduced rapidly, potentially with reduced assessment |
Important Note: Emergency changes bypass normal assessment for speed but require post-implementation reviews to capture issues and prevent future emergencies.
Processes
Change Enablement Planning and Optimization
Change enablement initiation
Establish or review scope, policies, and procedures
Change review and planning
Review planned changes, assess dependencies, coordinate scheduling
Change model and procedure improvement
Identify and propose enhancements
Communication
Communicate procedural changes across the organization
Change Lifecycle Management
Change registration
Record request with essential details
Change assessment
Evaluate risk, impact, resource requirements, dependencies
Change authorization
Submit to appropriate change authority for approval
Change planning
Plan implementation steps, timing, rollback procedures
Change realization control
Monitor implementation against the plan
Change review and closure
Review outcomes, document lessons learned, close record
Key Terms
Change authority: Person or group responsible for authorizing changes; different types may have different authorities.
Request for Change (RFC): Description of a proposed change used to initiate the enablement process.
Change model: Repeatable approach to managing a particular change type, defining steps, roles, timescales, and escalation procedures.
Change schedule: Calendar showing planned and historical changes, used to coordinate implementation and avoid conflicts.
Recommendations for Practice Success
- Prioritize enabling changes rather than restricting them
- Ensure all stakeholders understand change rationales and success criteria
- Delegate authority; not every change needs executive approval
- Leverage automation capabilities extensively
- Clarify dependencies between practices
- Avoid unnecessary complexity
- Remove irrelevant bureaucracy while adding efficiency incrementally
- Conduct thorough pre-authorization assessment to prevent later problems
Key Metrics
| Metric | What It Measures |
|---|---|
| Satisfaction with change outcomes and timeliness | Stakeholder perception of quality |
| Success and acceptance rate | Percentage of successful implementations |
| TPI of change | Time, cost, and quality performance index |
| Change realization time per model | Speed of implementation by type |
| Incidents related to change | Failures caused by changes |
| Changes as sources of errors/problems | How often changes introduce new issues |
| Satisfaction with change procedures | Ease of navigating the process |
| Compliance and non-compliance changes | Ratio of compliant to non-compliant changes |
| Change-related compliance incidents | Regulatory or policy violations |
Key Roles
- Change manager: Coordinates the enablement process and manages the change schedule
- Change coordinator: Supports assessment and planning activities
- Change authority: Person or group responsible for authorizing changes
Software Tools
- Workflow and collaboration tools
- Knowledge management tools
- Work planning and prioritization tools
- Analysis and reporting tools
- Orchestration tools for automated standard changes
90-Day Implementation Checklist
Month 1: Foundation
- Define change types (Standard, Normal, Emergency)
- Create RFC template with mandatory fields
- Establish Change Advisory Board (CAB) meeting cadence
- Define change authority matrix
- Document change calendar and maintenance windows
- Set up change record tracking in ITSM platform
Month 2: Process Maturity
- Create Standard Change catalogue (5-10 most common pre-approved changes)
- Implement change schedule visibility
- Establish Post-Implementation Review (PIR) process
- Set up CI/CD pipeline integration for automatic change records
- Define rollback requirements by category
- Begin tracking success rate and emergency change ratios
Month 3: Optimization
- Analyze change failure patterns
- Reduce emergency change ratio to under 5%
- Implement automated pre-deployment checks
- Measure lead time, failure rate, and emergency ratios
- Conduct quarterly CAB effectiveness reviews
- Update Standard Change catalogue with lessons learned