2.6.

Let’s now look at the concept of value streams and how they fit into the service value chain.

The service value chain is an operating model that outlines the key activities required to respond to demand and facilitate value creation.

Value streams use the service value chain activities to create value in specific scenarios.

Not every value stream uses all service value chain activities.

The service value chain includes six activities: plan, improve, engage, design and transition, obtain or build, and deliver and support.

These activities are flexible and can be combined in different ways depending on the type of service being delivered.

By combining value streams with the service value chain, organisations can design efficient and effective ways to deliver value.

Understanding how value streams and the service value chain work together is important for managing services effectively.

---

2. How this applies to TakeCars (car-rental marketplace)

This section explains how TakeCars should structure operations instead of thinking in departments or features.

a) TakeCars does not have “one process” — it has multiple value streams

Different customer scenarios = different value streams:

• Short city rental
• Airport pickup
• Long-term rental
• Replacement vehicle during breakdown

Each uses different combinations of service value chain activities.

Trying to force one rigid flow on all of them creates friction.

---

b) Mapping TakeCars to the service value chain

Plan

• Pricing rules
• Supplier eligibility
• Risk policies

Engage

• Search
• Booking
• Customer communication
• Supplier messaging

Design & Transition

• New rental flows
• Insurance options
• Supplier onboarding

Obtain / Build

• Platform features
• Integrations
• Contracts

Deliver & Support

• Handover
• Support during rental
• Issue resolution
• Refunds

Improve

• Reviews
• Incident analysis
• Policy refinement

This lens helps prioritise work logically instead of emotionally.

---

c) Why flexibility matters for TakeCars scale

ITIL explicitly states:

Not every value stream uses all activities.

For TakeCars:

• Repeat customers skip “design”
• Automated suppliers skip “engage-heavy” steps
• Crisis scenarios emphasise “deliver & support”

This legitimises simplification, not bureaucracy.

---

3. Key ideas to read right before the exam (high-yield)

This topic often appears as “how do these concepts relate?” questions.

Service value chain (memorise the six)

• Plan
• Improve
• Engage
• Design and Transition
• Obtain / Build
• Deliver and Support

If one is missing or replaced → answer is wrong.

---

Relationship logic (exam favourite)

Correct understanding:

• Value streams use service value chain activities
• Service value chain activities are building blocks
• Value streams are scenario-specific

Wrong logic:

• Value streams and service value chain are the same
• Every value stream uses all activities
• Activities are sequential and rigid

---

Fast exam shortcut

If the question asks:

• “How does X create value?” → value stream
• “What activities are involved?” → service value chain

---

One-line exam anchor

Value streams apply service value chain activities to create value in specific scenarios.

Keep this sentence in mind — it resolves most related exam questions.

---

This completes the current batch

You have now covered:

• Services & value
• Relationships & stakeholders
• Products, offerings, and value streams
• Service value chain integration

At this point, you are well ahead of the average ITIL Foundation candidate because you understand how everything fits together, not just definitions.

If you want, next we can:

• Continue with the next SRT
• Create a one-page TakeCars-as-ITIL model
• Or generate a 10-minute exam cram sheet based only on what you’ve uploaded so far

Just upload the next file or tell me how you want to proceed.