The New ITIL (Version 5): Value Streams Deliver Flow, Experience Delivers Value
# ITIL
# Value Streams
How ITIL (Version 5) integrates experience management with value stream thinking to ensure services create value that users can actually feel
March 16, 2026
Scott Everett
The New ITIL (Version 5): Value Streams Deliver Flow, Experience Delivers Value
Organisations across every sector have invested heavily in value stream thinking. We have mapped processes end-to-end, reduced handoffs, improved flow efficiency and aligned activity to outcomes. On paper, many services have never looked healthier.
Yet a persistent question remains.
If our value streams are working, why are users still frustrated?
This is where ITIL (Version 5) introduces a crucial evolution in service management thinking. It does not replace value streams. It strengthens them by placing equal weight on experience. Because a service that flows efficiently is not automatically a service that feels effective, trusted or valuable to the people using it.
Value streams show us how value should move. Experience shows us whether value is actually realised.
When a “good” value stream is not good enough
A well-designed value stream is structured, measurable and optimised. Activities are sequenced logically. Roles are defined. Metrics are monitored. Bottlenecks are identified and addressed. From an operational perspective, this is a significant achievement.
However, users do not experience our internal structure. They experience the journey.
Take a common digital service journey. A user submits a request. Data moves between systems. Notifications are triggered. Access is provisioned. Support is available if needed. Internally, the service may meet every defined target. Externally, the user may still encounter unclear instructions, duplicated messages, status uncertainty, or the need to repeat information across teams.
The process performs. The experience falters.
ITIL (Version 5) recognises this gap. It challenges organisations to look beyond whether the value stream works and ask whether the value is being experienced in a way that builds confidence and trust.
From operational performance to lived experience
Traditional service metrics focus heavily on efficiency and control. We measure lead time, throughput, resolution time and compliance against service levels. These measures remain important. They provide visibility and accountability.
However, experience management introduces a complementary lens. Instead of asking only how long something took, we ask how it felt. Instead of focusing solely on process adherence, we examine clarity, effort and understanding from the user’s perspective.
A service can meet its SLA and still create anxiety. It can resolve an incident within target and still leave the user uncertain about what happened. It can deliver a technically correct outcome that feels unnecessarily complex.
ITIL (Version 5) brings these perspectives together. It reframes service success as a balance between flow efficiency and experience effectiveness. The aim is not simply to deliver outputs, but to create meaningful, usable outcomes that users can navigate with confidence.
Experience management as a structural capability within the Product and Service Lifecycle
Experience management in ITIL (Version 5) is not an add-on survey mechanism. It is a structural capability that spans the Service Value System and is embedded across the Product and Service Lifecycle activities. This lifecycle recognises that services move continuously through stages such as discovery, design, acquire, build, transition, operate, deliver and support, often simultaneously across different work streams.
Experience must therefore be considered at every stage of this lifecycle, not just at the point of support or feedback collection. During discovery, organisations must understand user needs, expectations and context. During design, they must consider clarity, accessibility and usability. During build and transition, they must ensure that communications, training and onboarding support a smooth adoption. During support, they must provide reassurance, transparency and responsive support.
This lifecycle view reinforces that experience is not a single moment. It is the cumulative perception created across multiple interactions over time.
Importantly, experience exists across the entire value stream network. Services rarely operate in isolation. They depend on interconnected internal teams, suppliers, partners and supporting technologies. From the user’s perspective, these boundaries are invisible. They experience one service, not multiple organisational units.
If experience breaks down at a supplier handoff or between internal teams, the value stream may still function technically, but the perceived value deteriorates. ITIL (Version 5) encourages leaders to think beyond isolated streams and see the broader network of value creation.
Integrating experience into value stream design
Organisations that have already adopted value stream thinking do not need to start again. The shift is evolutionary rather than revolutionary, but it does require deliberate design choices and governance attention.
The first step is to layer experience insight onto existing value stream maps. This means identifying not only process steps but also user touchpoints, moments of uncertainty, emotional highs and lows, and areas where effort increases. When this perspective is added, improvement opportunities often become more visible because friction that was previously hidden within “successful” processes becomes explicit.
The second step is to broaden measurement. Operational indicators such as lead time and resolution time should be complemented by experience-focused measures such as perceived effort, clarity of communication and user confidence. These measures provide context to performance data and help organisations understand why a service that appears efficient may still be perceived as difficult or unreliable.
The third step is to design communication as part of the service, not as an afterthought. Many failures occur not because the service outcome is wrong, but because the user does not understand what is happening. Clear, timely and consistent communication at key stages of the value stream can significantly improve user confidence without requiring major system changes.
The fourth step is to reduce friction at organisational boundaries. Each handoff between teams, suppliers or systems introduces a risk to experience. Organisations should actively review these transition points, ensuring that context is preserved, duplication is minimised and accountability is clear from the user’s perspective.
The fifth step is to embed experience-led continual improvement. Experience insights should be reviewed alongside operational metrics in governance forums, service reviews and improvement backlogs. This ensures that improvement initiatives are driven not only by efficiency gains but also by meaningful enhancements to the user journey.
Finally, organisations should invest in capability development. Experience management requires skills in journey mapping, service design, communication and behavioural insight. Developing these capabilities within service management teams strengthens the ability to design services that are both efficient and intuitive.
A leadership perspective
In digital and application service environments, it is possible to achieve strong dashboards while still hearing frustration from users. That tension can be uncomfortable, particularly for teams that have worked hard to optimise processes and stabilise platforms.
ITIL (Version 5) provides a constructive way to address that tension. It legitimises experience as a core measure of service success. It reinforces that technical excellence and positive experience are not competing priorities, but complementary ones.
When organisations align value stream optimisation with deliberate experience design, service management moves from operational control to genuine value creation.
Conclusion
Value streams remain fundamental to modern service management. They enable clarity, alignment and improvement. However, they describe how value moves, not how value feels.
ITIL (Version 5) extends the discipline by embedding experience management into the heart of service thinking, supported by the Product and Service Lifecycle and a broader value stream network perspective. It recognises that value is not only produced; it is perceived.
The organisations that will lead in the next phase of digital service management will be those that optimise flow while intentionally shaping experience. They will understand that efficiency without empathy is incomplete.
In the end, a service is successful not because it worked internally, but because it worked for the people who relied on it.
Sign in or Join the community
Where conversation, connection, and real-world practices come together.
Create an account
Where conversation, connection, and real-world practices come together.
8
Comment (1)
Popular
Popular
Dive in
Related
Blog
ITIL (Version 5) and the Physics of Organizations: Why Flow of Value Beats Structure
By Sumit Jha • Mar 3rd, 2026 • Views 56
Blog
The New ITIL Version 5: What It Means in the Real World of Digital Services
By Scott Everett • Feb 5th, 2026 • Views 103
Blog
ITIL (Version 5) and the Physics of Organizations: Why Flow of Value Beats Structure
By Sumit Jha • Mar 3rd, 2026 • Views 56
Blog
The New ITIL Version 5: What It Means in the Real World of Digital Services
By Scott Everett • Feb 5th, 2026 • Views 103