Many service organizations track metrics diligently: ticket counts, resolution times, SLA compliance, and change volume. These are important metrics—but they often fail to answer the crucial question: Is the service really having the desired effect?
This is exactly where ITIL 5 —or rather, ITIL Version 5 comes into play. The new ITIL shifts the focus in management away from pure output toward outcome—that is, away from “What did we deliver?” toward “What has improved as a result?” This perspective is complemented by a greater emphasis on experience—specifically, the service experience from the users’ perspective.
Why Output Metrics Alone Can Be Misleading
Output is easy to measure. How many tickets were resolved? How quickly were responses provided? How many changes were implemented? However, a high level of activity is not automatically a sign of good service.
Typical real-world situations:
- The number of tickets is dropping because users are avoiding the service desk, not because the service has improved
- SLAs are being met, but users are still dissatisfied because of a lack of communication and transparency
- Many changes are being implemented, but the service remains unstable because the root causes are not being permanently resolved
- Fast processing doesn't help if the business misses its actual goal
ITIL Version 5 helps reduce these blind spots by integrating value and experience more closely into the management process.
Outcome: What ITIL 5 Means by “Outcome”
"Outcome" refers to the actual effect of a service. Examples:
- Employees can work productively because the systems are reliably available
- Customers enjoy a seamless experience because the services are easy to understand and work reliably
- Departments achieve their goals faster because service processes don't slow them down
- Risks are reduced because changes are implemented in a controlled and traceable manner
The key question in ITIL 5 is therefore: What results do we want to achieve—and which service decisions will help us achieve them?
As a result, service management is increasingly viewed as a contributor to value creation, rather than merely a support function.
Value: Management Based on Actual Benefits
ITIL 5 consistently embeds a value-oriented approach. Value is not created within the IT department, but rather through collaboration with stakeholders, processes, and users. For management, this means:
- Priorities are set based on benefit, not just on effort or history
- Decisions are guided more by goals than by habits
- Service development and service operations are viewed as a continuous cycle
This perspective is particularly crucial in digital organizations because services must constantly evolve. ITIL Version 5 provides the framework for this.
Experience: When Service Quality Is More Than Just Meeting SLAs
"Experience" describes how a service is actually perceived. Two services can be technically identical—yet be perceived in completely different ways. Factors such as communication, transparency, expectation management, and user guidance play an enormous role.
ITIL 5 reinforces this perspective and makes it clear: Service quality is driven not only by technology, but also by the service experience.
This gives rise to new policy initiatives:
- How easy is the request process for end users to understand?
- How transparent is the status of a request or issue?
- How clear is communication regarding changes and service interruptions?
- How quickly do users become able to work again—not just how quickly is a ticket closed?
How Organizations Practically Incorporate Outcomes and Experiences into Their Management Processes
ITIL Version 5 does not call for a new “flood of metrics.” On the contrary: less is often more. The key is to select metrics that enable decision-making.
Best Practices:
- Define a few, but meaningful, performance metrics for each service
- Continue to use output metrics, but always link them to outcome goals
- Systematically incorporate experience feedback, for example through brief satisfaction surveys
- Identify flow bottlenecks to implement improvements
In this way, management does not become mere reporting, but rather a tool for genuine growth.
Most Recent
Would you like to know why ITIL 5 is a particularly good fit for AI, automation, and DevOps, and how governance helps in this context? Then be sure to read the previous post:
"Designed with AI in Mind: Why ITIL Version 5 Is a Perfect Fit for AI, Automation, and DevOps"
Training Tip: ITIL Version 5 Foundation at SERVIEW
If you want to not only understand outcomes, value orientation, and experience, but also put them into practice in service management, the ITIL Version 5 Foundation training at SERVIEW is the ideal starting point. The training sessions began at SERVIEW in March and provide a hands-on look at how the new ITIL brings together governance, service quality, and value delivery.
Learn more now:
ITIL 5 Training Courses at SERVIEW
