Implementation Roadmap
A Six-Phase Approach to ITIL v5 Adoption
Implementing ITIL v5 represents a transformation programme that evolves organizational capabilities over time, rather than a project with a fixed endpoint. This roadmap provides a structured, repeatable approach scalable from small IT teams to large enterprises.
Overview of the Six Phases
| Phase | Name | Duration | Key Question |
|---|---|---|---|
| 1 | Assess | 4-6 weeks | Where are we now? |
| 2 | Envision | 3-4 weeks | Where do we want to be? |
| 3 | Design | 4-8 weeks | How do we get there? |
| 4 | Pilot | 6-12 weeks | Does it work in practice? |
| 5 | Scale | 12-26 weeks | Can we extend it across the organization? |
| 6 | Sustain | Ongoing | How do we keep improving? |
💡
Guiding Principle: "Start where you are." The first guiding principle applies directly to implementation -- assess current state honestly, build on what works, and improve incrementally.
Phase 1: Assess (4-6 weeks)
Objective
Establish evidence-based understanding of current ITSM maturity and identify gaps between present state and ITIL v5 ambitions.
Activities
1.1 Stakeholder Mapping and Engagement
- Identify stakeholder groups: executive sponsors, IT leadership, product teams, operations, service desk, business units, external partners
- Conduct structured interviews understanding pain points, strategic objectives, perceived maturity, and change appetite
- Create stakeholder influence/interest matrix for communication guidance
1.2 Current-State Assessment
- Audit existing processes against 34 ITIL management practices, documenting existence, maturity level, effectiveness, and alignment
- Map current workflows to 8-stage Product and Service Lifecycle (Discover through Support)
- Assess organizational structure and team collaboration patterns
- Review governance structures for decision-making authority
1.3 Gap Analysis
- Compare current state against ITIL v5 framework producing prioritized gap list
- Classify gaps by business impact (high/medium/low) and implementation complexity (high/medium/low)
- Use Maturity Assessment Guide for structured scoring
Outputs
- Stakeholder map with engagement strategy
- Current-state maturity report
- Prioritized gap analysis
- Executive summary for sponsor review
Phase 2: Envision (3-4 weeks)
Objective
Define target state -- what ITIL v5 adoption means for the specific organization.
Activities
2.1 Define the Target Operating Model
- Select appropriate value chain pattern(s)
- Determine which 8 lifecycle activities will be performed internally versus outsourced
- Design target team structure using Operating Model Design guidance
- Determine governance pattern matching organizational authority needs
2.2 Set Strategic Objectives
- Define 3-5 strategic objectives (examples: "Reduce incident resolution time by 30%", "Establish AI governance framework", "Achieve ISO 20000 readiness")
- For each objective, specify target metrics, measurement method, timeline, and accountable owner
- Align objectives with broader organizational strategy
2.3 Define Success Criteria
- Agree on quantitative and qualitative success metrics per phase
- Establish baseline measurements from Phase 1 for tracking progress
- Define governance cadence (recommended: monthly steering committee, quarterly board update)
Outputs
- Target state vision document
- Strategic objectives with success criteria
- Target operating model description
- Executive approval to proceed
Phase 3: Design (4-8 weeks)
Objective
Design detailed implementation plan including process designs, organizational changes, technology requirements, and training plans.
Activities
3.1 Process and Practice Design
- For each prioritized practice, design target-state process: triggers, inputs, activities, outputs, roles, metrics
- Map practices to lifecycle activities they enable or support
- Design interfaces between practices (e.g., Incident Management triggering Problem Management)
3.2 Organizational Design
- Define new or updated roles and responsibilities using ITIL Roles reference
- Design RACI matrix for each lifecycle activity
- Plan team restructuring including timeline, communication, and transition support
- Address four dimensions: Organizations and People, Information and Technology, Partners and Suppliers, Value Streams and Processes
3.3 Technology Planning
- Assess current ITSM tooling against v5 requirements
- Identify tool gaps (AI governance dashboard, experience measurement, value stream visualization)
- Evaluate tool options using Automation Tools reference
- Plan configuration changes for existing tools
- Consider observability and monitoring requirements
3.4 Training and Communication Plan
- Design role-based training curriculum
- Plan ITIL v5 certification for key staff
- Create communication plan with key messages for stakeholder groups
- Plan change champion network (1-2 champions per team)
Outputs
- Detailed process designs
- Organizational change plan
- Technology roadmap
- Training and communication plan
- Implementation budget and timeline
Phase 4: Pilot (6-12 weeks)
Objective
Test designed solutions in controlled environment to validate assumptions and refine approach before full rollout.
Activities
4.1 Select Pilot Scope
- Choose 1-3 services or products for pilot
- Selection criteria: willing team, manageable complexity, representative environment, measurable outcomes
- Define clear scope boundaries
4.2 Execute the Pilot
- Implement designed processes for selected scope
- Deploy tooling changes in controlled manner
- Provide intensive support and coaching for pilot teams
- Collect data continuously: process metrics, user feedback, team observations
4.3 Evaluate and Refine
- Compare pilot results against Phase 2 success criteria
- Conduct retrospectives with pilot teams
- Document lessons learned and required adjustments
- Update process designs, training materials, and tooling based on findings
Outputs
- Pilot results report
- Refined process designs
- Updated rollout plan incorporating lessons learned
- Go/no-go recommendation for scaling
Phase 5: Scale (12-26 weeks)
Objective
Extend proven pilot approach across organization in structured, managed manner.
Activities
5.1 Plan the Rollout Waves
- Group services/products/teams into rollout waves based on readiness, dependency, criticality, geographic factors
- Define cadence: teams per wave and interval between waves
- Establish support model with dedicated implementation coaches per wave
5.2 Execute Rollout
- Deploy processes, tools, and training to each wave
- Provide transition support: dedicated coaching, drop-in clinics, FAQ resources
- Monitor adoption metrics: are teams using new processes or reverting to old habits?
- Address resistance proactively using Change Leadership approach
5.3 Governance and Oversight
- Hold weekly implementation stand-ups with wave leads
- Provide monthly progress reports to steering committee
- Escalate blockers and risks through governance channel
- Adjust rollout plan based on emerging issues
Outputs
- Completed rollout across all waves
- Updated process documentation reflecting real-world refinements
- Transition of ownership from implementation team to operational teams
Phase 6: Sustain (Ongoing)
Objective
Transition from implementation mode to continuous improvement mode, ensuring adoption remains effective and evolves with organization.
Activities
6.1 Establish Continual Improvement Cadence
- Implement Continual Improvement model for ongoing practice optimization
- Maintain CI register: living backlog of improvement opportunities
- Schedule regular practice reviews (recommended: quarterly per practice area)
- Assign continual improvement owner or team
6.2 Performance Monitoring
- Implement ongoing measurement using defined KPIs
- Create executive dashboards reporting against strategic objectives
- Conduct periodic maturity assessments (recommended: annually)
6.3 Knowledge Management
- Document and share best practices across teams
- Maintain knowledge base of process documentation, templates, guides
- Establish communities of practice for cross-team learning
6.4 External Alignment
- Monitor ITIL v5 updates and Practice Guide releases from PeopleCert
- Maintain ISO alignment if applicable
- Participate in broader ITSM community for benchmarking and knowledge exchange
Outputs
- Continual improvement register and cadence
- Ongoing measurement and reporting
- Sustained capability maturity
Common Implementation Pitfalls
| Pitfall | Consequence | Mitigation |
|---|---|---|
| Skipping the Assess phase | Building on assumptions rather than evidence | Invest time understanding starting point |
| Over-designing before piloting | Months of design work invalidated by reality | Design enough to pilot; refine based on evidence |
| Under-investing in training | Teams don't understand or commit to new ways | Role-based training with ongoing coaching |
| Ignoring organizational change | Process changes fail because culture and behaviour don't follow | Integrate Culture Transformation from day one |
| No executive sponsorship | Implementation lacks authority to drive change | Secure executive sponsor before starting |
| Treating it as an IT project | Excludes business stakeholders essential for value creation | Frame as business transformation involving IT |
Related Pages
- Maturity Assessment Guide (structured scoring approach)
- Operating Model Design (team topology and patterns)
- Measuring Success (KPIs, OKRs, XLAs)
- Change Leadership (managing organizational resistance)
- Continual Improvement (the 7-step improvement model)
Last updated on April 2, 2026
ITIL® is a registered trademark of PeopleCert. © 2026 ITIL v5 Compass