Change Leadership
Leading organizational change for ITIL v5 adoption
Organizational Change Management (OCM) is one of ITIL v5's 34 management practices. This page extends that practice with leadership-level guidance for driving the human side of ITIL v5 adoption.
The change leadership framework
Three levels of change
| Level | Scope | Leader's Role | Example |
|---|---|---|---|
| Individual | How one person changes their behaviour | Coach and support | A developer learns to write post-mortem reports |
| Team | How a team changes its working practices | Facilitate and model | An ops team adopts blameless retrospectives |
| Organizational | How the organization changes its culture and systems | Sponsor, direct, and govern | Enterprise-wide ITIL v5 adoption |
Effective change leadership addresses all three levels simultaneously. Organizational change that ignores individual and team change will not sustain.
Stakeholder mapping and engagement
The influence/interest matrix
| Priority | Low Interest | High Interest |
|---|---|---|
| High Influence | Keep satisfied: Board members, CFO. Provide regular updates; involve in key decisions | Manage closely: CIO/CTO, IT Director, product leads. Active partnership and co-creation |
| Low Influence | Monitor: External vendors, peripheral teams. Minimal communication; update as needed | Keep informed: IT practitioners, end users. Regular communication; collect feedback |
Key stakeholder groups and their concerns
| Stakeholder | Primary Concern | Engagement Strategy |
|---|---|---|
| Board/Executives | "Will this deliver business value?" | Business case with ROI projections. Quarterly progress reports. |
| Middle management | "How will this affect my team?" | Involve early in design. Protect their authority. |
| IT practitioners | "Will I have to learn new things? Is my job at risk?" | Training investment. Career development paths. |
| End users | "Will my services improve?" | Communicate improvements. Solicit feedback. |
| Union/employee representatives | "Are jobs being eliminated?" | Transparent communication. Redeployment plans. |
| External suppliers | "Will contracts change?" | Early engagement. Joint transition planning. |
The eight-step change model (adapted from Kotter)
1. Create urgency
Communicate why ITIL v5 adoption is necessary now, not someday:
- Share competitive intelligence (what are peers and competitors doing)
- Highlight current pain points with evidence (incident costs, SLA breaches, employee turnover in IT)
- Connect ITIL v5 capabilities to specific business challenges (AI governance, product lifecycle, experience measurement)
2. Build a guiding coalition
Assemble a coalition of influential leaders across the organization:
- Executive sponsor (CIO or CTO)
- Change champion from each major team
- External advisor (consultant, industry peer)
- Employee representative
3. Form a strategic vision
Articulate a clear, compelling vision for the future state:
- What will be different after ITIL v5 adoption
- What value it will deliver to customers, employees, and the organization
- What the journey will look like (not just the destination)
4. Enlist a volunteer army
Change does not succeed through a small project team alone. Build momentum through:
- Identifying enthusiastic early adopters and empowering them
- Creating visible rewards for adoption and improvement
- Providing forums for sharing success stories
5. Enable action by removing barriers
Identify and address obstacles to change:
- Process barriers: Outdated approval processes that conflict with new ways of working
- Technology barriers: Inadequate tooling that forces manual workarounds
- Organizational barriers: Siloed team structures that prevent cross-functional collaboration
- Skills barriers: Knowledge gaps that prevent people from working effectively
- Cultural barriers: Fear of failure, blame culture, resistance to transparency
6. Generate short-term wins
Plan and deliver visible improvements within the first 90 days:
- Quick-win improvements that demonstrate ITIL value (e.g., reduced incident resolution time through better categorization)
- Visible process improvements that teams can feel immediately
- Celebrate and communicate wins widely
7. Sustain acceleration
Do not declare victory too early. Build on momentum:
- Expand successful pilots to additional teams and services
- Address systemic issues that become visible during scaling
- Continue investing in training and coaching
- Maintain the guiding coalition's energy and commitment
8. Institute change
Embed changes into the organization's DNA:
- Update job descriptions and competency frameworks
- Align performance management with new behaviours
- Embed ITIL practices into onboarding for new employees
- Make continual improvement a permanent capability, not a project
Managing resistance
Understanding resistance
Resistance is a natural response to change, not a character flaw. Common sources:
| Source of Resistance | Root Cause | Leadership Response |
|---|---|---|
| Fear of incompetence | "I don't know how to do this new thing" | Invest in training and coaching. Provide safe spaces to practice. |
| Loss of status or power | "My expertise is being devalued" | Involve experienced staff as mentors and subject matter experts. |
| Disruption to routines | "I know how to do my job; why change?" | Explain the "why" clearly. Show how new approaches reduce pain. |
| Distrust of leadership | "This is just another management fad" | Be honest about past failures. Demonstrate commitment through action, not just words. |
| Legitimate concerns | "This approach has real flaws" | Listen genuinely. Adapt the approach. Resistance often contains valuable feedback. |
⚠️
The most valuable resistance is legitimate concern. If your most experienced practitioners are pushing back, they may be seeing problems that your change team has missed. Treat resistance as signal, not noise.
Communication strategy
| Audience | Channel | Frequency | Key Message |
|---|---|---|---|
| All staff | Town hall/all-hands | Monthly | Vision, progress, upcoming changes |
| IT teams | Team meetings | Weekly | Specific changes affecting their work |
| Leadership | Steering committee | Bi-weekly | Progress, risks, decisions needed |
| Change champions | Champion network meeting | Weekly | Support, enablement, issue escalation |
Communication principles
- Explain the "why" before the "what." People accept change more readily when they understand the reason.
- Be honest about difficulties. Sugarcoating builds distrust. Acknowledge that change is hard.
- Use stories, not just data. Personal stories of how a new practice helped someone are more persuasive than metrics.
- Listen more than you talk. Two-way communication builds trust.
- Communicate frequently. Under-communication is a bigger risk than over-communication during change.
Measuring change effectiveness
| Metric | Method | Target |
|---|---|---|
| Awareness | Survey: "Do you understand the ITIL v5 changes?" | > 90% |
| Understanding | Assessment: can people explain the key changes | > 75% |
| Commitment | Survey: "Do you support the changes?" | > 60% (initial), > 80% (sustained) |
| Adoption | Usage data: are new processes being used? | > 80% compliance within 6 months of rollout |
| Proficiency | Performance data: are people using processes effectively? | Improving trend |
| Sustainability | 12-month check: are changes still in place? | > 90% retention |
Related pages
- Culture Transformation (the cultural foundation for change)
- Implementation Roadmap (where change leadership fits in adoption)
- Business Case & ROI (justifying the change)
- Organizational Change Management (the ITIL practice)
Last updated on April 2, 2026
ITIL® is a registered trademark of PeopleCert. © 2026 ITIL v5 Compass