14 practices
Architecture Management, Information Security, Measurement & Reporting, Portfolio, Project, Relationship, Risk, Supplier, Workforce & Talent and related capabilities.
Element 4
Embed capability where it matters most across 34 ITIL 4 practices.
ITIL 4 practices replace rigid process thinking with flexible, reusable capabilities that can be embedded across strategy, service delivery, support and continual improvement.
The goal is not to launch all 34 at once, but to prioritise, document, automate and measure the capabilities that matter most to your services and value streams.
17 practices
Availability, Capacity, Change, Incident, Asset, Monitoring, Problem, Release, Catalogue, Service Desk, Service Level, Request, Continuity and supporting delivery practices.
3 practices
Deployment Management, Infrastructure & Platform Management, and Software Development & Management.
Prioritise, own, integrate and measure.
Identify critical practices, assign ownership, align policy and tooling, and enable cross-practice collaboration with clear metrics and accountability.
Implementation guidance
- Assess and prioritise the practices that matter most to current services and value streams.
- Define roles, practice owners, RACI models and operating boundaries.
- Document policies, procedures and standards in a just-enough, reusable format.
- Integrate tooling, automate repetitive steps and align measures to service outcomes.
Evidence
What good practice enablement produces.
- Documented workflows, policies, SOPs and templates.
- Clear ownership, stakeholder accountability and role boundaries.
- Tool configuration evidence such as workflows, forms or approval paths.
- Practice-specific KPIs and logs, from incidents to change schedules.
- Cross-practice evidence such as incident-to-problem or change-to-release linkage.
Examples by practice
ServiceNow and Jira workflows for Change, CMDB and discovery tooling for Configuration, CI/CD and infrastructure automation for Deployment, knowledge bases for Knowledge Management, and GRC tooling for Risk and Compliance.
Track maturity, performance and automation.
Practice maturity, SLA/OLA compliance, backlog volume, first contact resolution, mean time to resolve and automation coverage all help show whether capability is actually improving.
Too much, too fast.
Avoid launching too many practices at once, unclear ownership, tooling mismatch and documentation overload. Prioritise by risk, maturity and value stream need, then iterate.
Capability rollout in phases.
Weeks 1–2 assessment and prioritisation, Weeks 3–6 workflow and documentation design, Weeks 7–10 automation and metrics enablement, then ongoing improvement cycles.