Practice (ITIL 5 sense)

A set of organizational resources and capabilities designed to perform work or accomplish an objective, used flexibly across different value streams.

The concrete, often tool-supported sequence of tasks and handoffs that implements a value stream in day‑to‑day operations.

In ITIL 5, a set of organizational resources and capabilities designed to perform work or accomplish an objective, used flexibly across different value streams.

The concrete sequence of tasks, handoffs, and tool-supported actions that implements a value stream in daily operations.

What is Change enablement?

A service management practice that ensures changes to services and components are assessed, authorized, and implemented in a controlled way, balancing risk and value.

What is Incident management?

A service management practice focused on minimizing the negative impact of incidents by restoring normal service operation as quickly as possible.

Service Value Streams, Workflows, and the ITIL 5 Practices Landscape — ITIL Foundation (Version 5) Exam Prep Bootcamp

From ITIL 4 to ITIL 5: Why Value Streams Matter

Why value streams?

ITIL 5 builds on ITIL 4 but shifts attention away from memorizing processes toward understanding how value flows end‑to‑end through the organization.

From processes to flow

Earlier ITIL versions led many teams to optimize individual processes. ITIL 5 emphasizes service value streams so that the whole path from demand to value is optimized.

Key building blocks

You will work with three ideas together: the Service Management System (SMS), service value streams and workflows, and practices as flexible capability sets along the value stream.

The Service Management System and Where Value Streams Fit

Recap: the SMS

The Service Management System (SMS) is the overall framework of governance, management practices, policies, processes, and continual improvement that shapes how services are managed.

Where value streams sit

Service value streams live inside the SMS. They describe how specific types of value are created, step by step, by combining parts of several practices.

City metaphor

Imagine the SMS as a city, practices as the buildings and services, and each service value stream as the actual route people take through the city to reach a valuable outcome.

What Is a Service Value Stream in ITIL 5?

Definition

A service value stream is the end‑to‑end sequence of activities an organization performs to respond to a specific type of demand and deliver a specific type of value.

Examples

Typical value streams include: request a standard laptop, resolve an incident, onboard a new employee, or release a new feature. Each is a distinct path from demand to value.

Activities inside a stream

Value streams are often broken into activities like Engage, Plan, Design and build, Deliver and support, and Improve. Different practices support each of these activities.

Walkthrough: A Simple Incident Resolution Value Stream

Step 1: Demand appears

A student cannot connect to campus Wi‑Fi and raises an issue via the self‑service portal. Engage activities use service desk and incident management practices.

Step 2–3: Triage and diagnosis

The service desk logs and categorizes the incident, then network operations correlate multiple incidents and identify a failing controller using monitoring and problem management.

Step 4–5: Fix and learn

The network team fails over to a backup controller, service is restored, the incident is closed, feedback is collected, and knowledge and improvement registers are updated.

Map a Value Stream in Your Own Words

5. Interactive: Map a Value Stream in Your Own Words

Activity (3–4 minutes):

Pick a simple IT service you know (for example, printing in a lab, password reset, or booking a study room).
On paper or in a notes app, write a short "demand to value" story:

Who has the need?
How do they express it?
What steps happen behind the scenes?
How do they know the need is satisfied?

Under each step, quickly note which practices might be involved. Use broad labels such as:

Service desk / support
Incident or request management
Change enablement
Asset and configuration management
Release / deployment
Information security management

Reflection questions:

Where did governance or risk show up implicitly? (For example, approvals, policy checks.)
Which step looks like the biggest bottleneck? That is where continual improvement might focus.

Write 2–3 bullet points summarizing:

The value stream you chose
The 2–3 most important practices supporting it

Keep this example in mind; we will link it to ITIL 5 practice types next.

ITIL 5 Practices: Types and Roles Across the Lifecycle

Practice-based approach

ITIL 5 uses practices, not rigid processes. Practices are organizational capabilities that can be combined flexibly across different value streams and workflows.

Three practice types

General management practices support overall management, service management practices support services, and technical management practices provide specialized technical capabilities.

Roles across a stream

General practices shape policies and risk, service practices run daily workflows, and technical practices implement and operate technology along the value stream.

Check Understanding: Practices Along a Value Stream

7. Quiz: Practices Along a Value Stream

Read the question carefully, then choose the best answer.

In an "onboard a new employee" value stream, which combination best matches the practices typically involved across the stream?

Only incident management, because every onboarding step is treated as an incident.
Service request management and change enablement only, because technical practices are not part of value streams.
Service request management for handling the onboarding request, plus supporting practices such as access management, change enablement, and technical practices like infrastructure and platform management.

Show Answer

Answer: C) Service request management for handling the onboarding request, plus supporting practices such as access management, change enablement, and technical practices like infrastructure and platform management.

Onboarding a new employee is usually handled as a service request, but it also requires access management, change enablement for provisioning, and technical practices to configure devices and platforms. Value streams typically involve multiple practices working together.

Linking Value Streams, Workflows, and Controls

Value and control together

ITIL 5 expects value creation to stay under control. Governance, risk management, and controls are embedded into value streams and workflows, not bolted on later.

Controls inside workflows

Typical controls are built into steps: approvals in request workflows, security reviews before deployment, and automated tests and monitoring around releases.

Design and improvement

When you design or improve a value stream, you also design where controls live and ensure that changes do not undermine governance or risk management.

Review: Key Terms for ITIL 5 Value Streams and Practices

9. Flashcards: Key Terms

Use these cards to quickly review the core ideas before the final activity.

Service Management System (SMS): The overall management framework for how an organization directs, plans, delivers, supports, and improves services, including governance, practices, policies, and continual improvement.
Service value stream: An end‑to‑end sequence of activities an organization performs to respond to a specific type of demand and deliver a specific type of value.
Practice (ITIL 5 sense): A set of organizational resources and capabilities designed to perform work or accomplish an objective, used flexibly across different value streams.
Workflow: The concrete, often tool-supported sequence of tasks and handoffs that implements a value stream in day‑to‑day operations.
General management practices: Practices that support the overall management of the organization, such as continual improvement, information security management, and risk management.
Service management practices: Practices that directly support services across their lifecycle, such as incident management, service request management, and change enablement.
Technical management practices: Practices that provide specialized technical capabilities, such as infrastructure and platform management, software development and management, and deployment management.

Exam Focus: High‑Priority Practices and Typical Questions

High‑priority practices

Expect many questions on incident, service request, change enablement, release and deployment, service desk, problem, service level, configuration, security, risk, and continual improvement.

Question patterns

Questions often ask which practice is most involved in a scenario or how practices and value streams relate. Correct answers emphasize multiple practices supporting a single value stream.

Reasoning strategy

Identify the part of the value stream a question targets, then choose the practice that is central at that stage, keeping governance and continual improvement in mind.

Final Activity: Build a Mini Value Stream Map

11. Final Activity: Build a Mini Value Stream Map

Spend 3–4 minutes consolidating what you learned.

Choose one of these value streams (or reuse your earlier example):

Reset a forgotten password
Provision a standard laptop
Release a small software enhancement

For your chosen stream, write a 5–7 step list from demand to value. Example structure:

User expresses need (how?)
Request or incident is logged and categorized
Work is approved or scheduled
Technical work is done
Service is confirmed and closed
Feedback is captured
Improvement ideas are recorded

Under each step, note 1–2 practices that are most important there.

Add a final bullet: "Where would I place a key control?"

For example, an approval step, a security check, or an automated test.

If you can do this quickly for multiple scenarios, you have a solid grasp of service value streams, workflows, and the ITIL 5 practice landscape.

Key Terms

Practice: In ITIL 5, a set of organizational resources and capabilities designed to perform work or accomplish an objective, used flexibly across different value streams.
Workflow: The concrete sequence of tasks, handoffs, and tool-supported actions that implements a value stream in daily operations.
Change enablement: A service management practice that ensures changes to services and components are assessed, authorized, and implemented in a controlled way, balancing risk and value.
Incident management: A service management practice focused on minimizing the negative impact of incidents by restoring normal service operation as quickly as possible.
Service value stream: An end‑to‑end sequence of activities that an organization performs to respond to a specific type of demand and deliver a specific type of value to customers and stakeholders.
Service request management: A service management practice for handling user requests that are pre-approved and low risk, such as information requests or standard service access.
General management practices: Practices that support the overall management and governance of the organization, such as continual improvement, information security management, and risk management.
Service management practices: Practices that directly support services throughout their lifecycle, such as incident management, service request management, change enablement, and service level management.
Technical management practices: Practices that provide specialized technical capabilities to support the service value streams, such as infrastructure and platform management, software development and management, and deployment management.
Service Management System (SMS): The overall management framework that defines how an organization directs, plans, delivers, supports, and improves services, including governance, practices, policies, and continual improvement.