ITIL 4 is the current version of ITIL, the most widely used framework for IT service management. It describes 34 practices, seven guiding principles, and a service value system, and it is designed to work alongside Agile, DevOps, and Lean rather than against them.

ITIL has a reputation for being heavy, and the older versions earned it. ITIL 4 is deliberately lighter: it tells you what good looks like and leaves the how to you. Used that way, it is a useful reference. Used as a rulebook, it becomes the bureaucracy everyone complains about.

From lifecycle to value system

ITIL v3 organized everything around a service lifecycle: strategy, design, transition, operation, and continual improvement. Each stage had its own processes, and the model worked well for planned, waterfall-style change. It worked less well for teams that deploy daily.

ITIL 4 replaces the lifecycle with the service value system. The system has five parts: guiding principles, governance, the service value chain, practices, and continual improvement. The idea is that value is created by activities working together, not by passing work from one stage to the next.

The service value chain has six activities: plan, improve, engage, design and transition, obtain and build, and deliver and support. An organization does not have to do them in order, and it does not have to do all of them for every piece of work. A small change might use only two. A new service might use all six.

The seven guiding principles

The guiding principles are the most practical part of ITIL 4, because they apply to every decision. Focus on value means judging work by what it does for the customer, not by whether the process was followed. Start where you are means improving what exists instead of rebuilding from scratch.

Progress iteratively with feedback means making small changes and checking they worked, rather than betting everything on a big one. Collaborate and promote visibility means working in the open, so problems surface early. Think and work holistically means considering the whole service, not just one part.

Keep it simple and practical means removing steps that add no value — the principle most ITIL implementations violate first. Optimize and automate means improving the manual work before automating it, because automating a bad process just makes bad things happen faster.

Note: The principles are the test for any ITIL practice you adopt. If a practice violates keep it simple and practical, the practice is wrong for your team, not your team for the practice. The framework says so itself.

The 34 practices

ITIL 4 describes 34 practices in three groups. General management practices include continual improvement, information security management, and risk management — the practices every organization needs, not just IT.

Service management practices are the familiar ones: incident management, problem management, change enablement, service request management, service level management, and service desk management. These are the practices most teams adopt first, and the ones this site’s tools support directly.

Technical management practices cover deployment management, infrastructure and platform management, and software development and management. These are where ITIL 4 meets DevOps most directly, and where the framework’s advice is intentionally high-level — the engineering details belong to the engineering team.

Certification and adoption

ITIL 4 has a certification path: Foundation, then Managing Professional or Strategic Leader, then Master. Foundation covers the key concepts and is the only level most people need. The higher levels are for people who design and run service management as a profession.

For adoption, the framework’s own advice is to start where you are and progress iteratively — which means adopting one practice at a time, driven by a real problem. A team that adopts incident management because outages are chaotic will succeed. A team that adopts all 34 practices because a consultant said so will not.

Measure each practice by whether it improved something you can name: faster recovery, fewer repeat incidents, fewer failed changes. If a practice does not improve a number, it is either implemented badly or not needed yet.

Try the tool

Service level management is one of the core ITIL 4 practices, and it starts with a number: the uptime percentage your service promises. The SLA uptime calculator converts any SLA percentage into the downtime it allows per month, quarter, and year, so the target you agree with the business is one you can actually measure and keep.