A specific combination of Service Value Chain activities that an organization follows to create value for a particular stakeholder or outcome.

Engage – typical practices

Service desk, relationship management, service level management, incident management (initial contact), service request management, supplier management.

Design and transition – typical practices

Change enablement, service design, release management, service validation and testing, project management.

An unplanned interruption to a service or reduction in the quality of a service.

A set of organizational resources designed for performing work or accomplishing an objective; ITIL 4 replaces the older, narrower idea of 'process' with practices.

What is Value stream?

A series of steps an organization undertakes to create and deliver products and services to consumers, turning inputs into outputs and outcomes.

What is Service request?

A request from a user or their representative that initiates a service action which has been agreed as a normal part of service delivery.

Linking It All: Practices Inside the Service Value Chain — ITIL 4 Foundation Exam Prep: Complete Syllabus, Exam-Focused

Q: A service desk agent receives a call about a failed online exam submission. They log the details, reassure the student, and explain the expected resolution time based on agreed targets. Which Service Value Chain activity is MOST central in this moment?

Engage. **Engage** is most central here because the focus is on interacting with the user, understanding the issue, and communicating expectations. Deliver and support will become central when the team starts technical diagnosis and resolution.

Big Picture: Value Streams Inside the ITIL 4 Service Value System

Service Value System and Chain

In ITIL 4, the Service Value System (SVS) shows how all parts of service management work together to create value. At its core is the Service Value Chain (SVC), a flexible model of activities.

Value Streams Defined

A value stream is a specific path of activities an organization follows to create value. You combine SVC activities in different sequences to form value streams for different situations.

Six Service Value Chain Activities

The six SVC activities are: 1) Plan, 2) Improve, 3) Engage, 4) Design and transition, 5) Obtain/build, 6) Deliver and support.

Stories, Not Isolated Steps

In exams and real life, you see stories: an incident resolved, a request fulfilled, a change deployed. Each story is a value stream made of SVC activities, supported by multiple practices.

Module Goals

You will map scenarios to SVC activities, see which practices are active, follow handoffs, and apply guiding principles and four dimensions. Remember: there is no single correct flow; ITIL 4 values flexibility.

The Six Service Value Chain Activities: Quick Reference

Plan and Improve

Plan aligns vision, status, and direction. Practices: strategy, portfolio, financial, service level, risk. Improve drives continual improvement via continual improvement, problem management, measurement, change, and knowledge.

Engage

Engage focuses on understanding stakeholder needs and maintaining relationships. Practices: service desk, relationship management, service level, incident (initial contact), request management, supplier management.

Design and Transition

Design and transition ensures products and services meet expectations for quality, cost, and time. Practices: change enablement, service design, release management, validation and testing, project management.

Obtain/Build

Obtain/build makes sure components are created or acquired when needed and at the right quality. Practices: software development, infrastructure management, supplier management, deployment, release management.

Deliver and Support

Deliver and support is where live services are actually delivered and supported. Practices: incident management, request management, service desk, problem management, monitoring, IT asset management.

Value Stream 1: Resolving an Incident (End‑to‑End Walkthrough)

Incident Scenario

Scenario: A student cannot access the university’s learning platform just before an online exam. We will trace this as a value stream and connect it to Service Value Chain activities and practices.

1. Engage

The student calls the service desk. The agent logs an incident, asks clarifying questions, and checks impact and priority. Practices: service desk, incident management, service level management.

2–3. Deliver and Support

The agent tries a quick fix using knowledge and monitoring data, then escalates to 2nd‑line. Practices: incident management, monitoring and event management, knowledge management, technical management, access management.

4. Improve

Many students are affected, so a problem record is opened. Root cause analysis begins to prevent recurrence. Practices: problem management, continual improvement, risk management.

5. Obtain/Build + Design and Transition

Developers prepare a configuration or code fix. The change is assessed, authorized, and scheduled. Practices: software development, change enablement, release management, validation and testing.

6–7. Deliver and Support + Improve

The fix is deployed, service recovers, the incident is closed, and lessons learned are captured. Practices: deployment, incident management, service desk, monitoring, problem management, knowledge management.

Practice: Spot the Activity and Practice (Incident)

Use this quick exercise to train your exam brain to map story fragments to SVC activities and practices.

For each statement, pause and answer mentally:

"The agent explains to the student how long the fix is expected to take based on agreed targets."

Which SVC activity is most central here?
Which practice is most visible?

"The operations team adjusts monitoring thresholds so that similar issues trigger alerts earlier."

Which SVC activity?
Which practice?

"The change authority reviews the risk of applying the fix during exam time."

Which SVC activity?
Which practice?

Scroll down for suggested answers.

---

Suggested answers:

Likely Engage (communicating expectations with a user), practice: service level management (targets) or service desk (communication channel). On the exam, if you must pick one, service level management is usually more specific to targets.

Likely Improve (adjusting monitoring to prevent or detect earlier), practice: monitoring and event management plus continual improvement.

Likely Design and transition (assessing changes before deployment), practice: change enablement with support from risk management.

Value Stream 2: Fulfilling a Service Request (Standard Request)

Service Request Scenario

Scenario: A new staff member needs a standard laptop and access to collaboration tools. This is a typical service request value stream, usually simpler than an incident.

1–3. Engage, Plan, Design and Transition

The manager submits a "New Starter" request via a portal. Planning (budget, stock, approvals) is mostly pre‑done, and a request model defines tasks and SLAs.

Practices in Early Steps

Practices: service request management, service desk, service level management, financial management, IT asset management, portfolio management, service design, change enablement (for the model).

4–5. Obtain/Build and Deliver and Support

A laptop is picked or ordered, imaged, and delivered; accounts and access are set up and confirmed. Practices: IT asset, infrastructure, supplier, deployment, request management, access management, service desk.

6. Improve

Feedback leads to updating the request model (e.g., adding a default collaboration tool). Practices: continual improvement, service request management, relationship management.

Value Stream 3: Deploying a Change (Planned Change)

Change Scenario

Scenario: The university rolls out a new version of the learning platform with improved exam features. We follow this planned change as a value stream.

1–2. Plan and Engage

The change is aligned with digital strategy and funded, then stakeholders and suppliers share requirements. Practices: strategy, portfolio, financial, relationship, business analysis, supplier, service level.

3–4. Design and Transition, Obtain/Build

Solution and transition are designed, then built and configured in test. Practices: service design, change, project, release, validation and testing, software development, infrastructure, deployment, configuration.

5–6. Authorize and Deploy

Test results are reviewed and deployment is approved. The new version is deployed, the service desk is briefed, and monitoring is updated. Practices: change, validation, risk, deployment, release, service desk, monitoring.

7. Improve

A post‑implementation review checks benefits and lessons learned, feeding future changes. Practices: continual improvement, change enablement, measurement and reporting.

Guiding Principles and Four Dimensions Along a Value Stream

Guiding Principles

ITIL 4 guiding principles include: focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, optimize and automate.

Four Dimensions

Four dimensions: 1) organizations and people, 2) information and technology, 3) partners and suppliers, 4) value streams and processes. These must all be considered for effective service management.

Applying Principles and Dimensions

In the incident stream, you keep workflows simple (value streams and processes), automate resets (information and technology), train the desk (organizations and people), and involve cloud providers (partners and suppliers).

Exam Tip

If a question asks why a decision is good practice, it often targets a guiding principle or dimension, not a specific process step. Link the story back to these higher‑level ideas.

Quiz: Map the Story to the Value Chain

Test your ability to pick the most relevant Service Value Chain activity in a scenario.

A service desk agent receives a call about a failed online exam submission. They log the details, reassure the student, and explain the expected resolution time based on agreed targets. Which Service Value Chain activity is MOST central in this moment?

Engage
Deliver and support
Improve
Plan

Show Answer

Answer: A) Engage

**Engage** is most central here because the focus is on interacting with the user, understanding the issue, and communicating expectations. Deliver and support will become central when the team starts technical diagnosis and resolution.

Flashcards: Key Terms and Links

Use these cards to reinforce core ideas about value streams, activities, and practices.

Value stream: A specific combination of Service Value Chain activities that an organization follows to create value for a particular stakeholder or outcome.
Service Value Chain (SVC): The central ITIL 4 model describing six activities (Plan, Improve, Engage, Design and transition, Obtain/build, Deliver and support) that can be combined into value streams.
Engage – typical practices: Service desk, relationship management, service level management, incident management (initial contact), service request management, supplier management.
Deliver and support – typical practices: Incident management, service request management, service desk, problem management, monitoring and event management, IT asset management.
Design and transition – typical practices: Change enablement, service design, release management, service validation and testing, project management.
Guiding principle: Focus on value: Always identify who the customer or stakeholder is and how each step in the value stream contributes to outcomes they care about.
Four dimensions of service management: Organizations and people; information and technology; partners and suppliers; value streams and processes.

Key Terms

Incident: An unplanned interruption to a service or reduction in the quality of a service.
Practice: A set of organizational resources designed for performing work or accomplishing an objective; ITIL 4 replaces the older, narrower idea of 'process' with practices.
Value stream: A series of steps an organization undertakes to create and deliver products and services to consumers, turning inputs into outputs and outcomes.
Service request: A request from a user or their representative that initiates a service action which has been agreed as a normal part of service delivery.
Change enablement: The ITIL 4 practice that maximizes the number of successful changes by ensuring that risks are properly assessed, and changes are authorized and scheduled.
Guiding principles: Recommendations in ITIL 4 that guide an organization in all circumstances, regardless of changes in its goals, strategies, or management structure.
Service Value Chain (SVC): A set of interconnected activities within the SVS that can be combined in flexible ways to form value streams for creating and delivering services.
Service Value System (SVS): The ITIL 4 model that describes how all components and activities of an organization work together as a system to enable value creation.
Four dimensions of service management: A holistic view of service management that considers organizations and people, information and technology, partners and suppliers, and value streams and processes.