SkarpChapter 9 of 19
The ITIL Digital Product and Service Lifecycle: Phases and Flow
Trace the journey of a digital product or service from initial discovery through design, build, transition, operation, and improvement, using ITIL’s lifecycle view as your map.
Orienting Yourself: Lifecycle vs Practices vs Value Chain
Three Overlapping Maps
ITIL 4 centers on the service value system and service value chain, but the exam still expects a lifecycle view of digital products and services. You must separate lifecycle, value chain, and practices.
Lifecycle View
The lifecycle is a time-based story: discovery → design → build → transition → operation → improvement. It answers: what typically happens first, next, and later for a digital service?
Service Value Chain
The service value chain is a set of activities (Plan, Improve, Engage, Design & transition, Obtain/build, Deliver & support) that combine into value streams used to co-create value.
Practices
Practices are capabilities like Incident Management or Change Enablement. They are not phases or steps; they are toolkits used across many phases and value chain activities.
Exam Mindset
On the exam, ask: Where in the lifecycle are we now, and which value chain activities and practices are most active here? This helps you decode scenario-based questions.
The Digital Product and Service Lifecycle: Big Picture
Six Phases at a Glance
Typical phases: 1) Discovery and demand shaping, 2) Design, 3) Build, 4) Transition, 5) Operation, 6) Continual improvement. These describe the journey of a digital service.
Inside the Service Value System
The lifecycle sits inside the service value system, which is "a model representing how all the components and activities of an organization work together as a system to enable value creation."
Value Co-creation
The lifecycle tells the story of value co-creation: "The joint activities performed by a service provider and a service consumer to create value." Both sides act in every phase.
Not a Waterfall
These phases are not rigid gates. In Agile and DevOps you often move through discovery, design, build, transition, operation, and improvement in short, repeated cycles.
Running Example
Keep one product in mind, like a food-delivery app, looping through these phases many times as it grows from pilot to mature, widely used digital service.
Phase 1: Discovery and Demand Shaping
What is Discovery?
Discovery turns raw ideas and pain points into shaped demand and opportunities. It starts before any code is written and focuses on understanding needs and context.
Key Stakeholders
You work with the customer, user, and sponsor. Customer defines requirements, user uses the service, sponsor authorizes budget for service consumption.
Typical Activities
You observe behavior, analyze trends and regulations, identify stakeholders, craft problem statements, and prioritize ideas against strategy and capacity.
Value Chain Link
Discovery mainly uses Engage and Plan activities in the service value chain, supported by practices like Business Analysis and Relationship Management.
Exam Trap
Discovery is a lifecycle phase, not a practice. Business Analysis is a practice that supports discovery, but they are not interchangeable terms on the exam.
Lifecycle in Action: Discovery and Design for a Food-Delivery App
Startup Discovery
A food-delivery startup sees local restaurants losing customers. They interview owners and diners and shape demand for a lower-fee, live-tracking delivery service.
From Idea to Shaped Demand
Discovery output: "A digital service that lets local restaurants receive and manage delivery orders with lower fees and live tracking for diners."
Designing the Service Offering
They define a service offering: basic order management, courier assignment, tracking, plus a premium tier with analytics for restaurants.
Utility and Warranty
Utility is the functionality: ordering, menus, tracking. Warranty is assurance: 45-minute delivery in the pilot area, 99.5% availability in opening hours.
Value Chain and Practices
Design mainly uses Design & transition and Plan activities, supported by Service Design, Architecture Management, and Service Level Management practices.
Phase 2: Design – From Shaped Demand to Service Blueprint
Purpose of Design
Design turns shaped demand into a blueprint. It balances utility (what the service does) and warranty (how reliably and securely it does it).
Key Design Activities
You define outcomes, service offerings, UX, data and integrations, support models, and non-functionals like security, compliance, and resilience.
Value Chain Focus
Design is mainly about Design & transition and Plan, with continued input from Engage as you refine requirements with stakeholders.
Print Portal Example
For a print portal, design covers login with university credentials, malware scanning, payment options, queue visibility, and support via chat.
Exam Signal
If a question mentions user journeys, service levels, support models, or end-to-end service behavior, think: design phase / Design & transition activity.
Phases 3 and 4: Build and Transition – Getting Ready for Live Use
Build Phase Focus
Build is about creating or configuring components: coding, configuring SaaS, setting up infrastructure, building integrations, tests, and documentation.
Build and the Value Chain
Build maps mainly to Obtain/build in the service value chain, supported by Software Development, Infrastructure Management, and Test Management practices.
Transition Phase Focus
Transition moves new or changed services into live use: planning releases, managing changes, testing, training, and updating configuration and docs.
Transition and the Value Chain
Transition relies on Design & transition and Obtain/build, and starts to touch Deliver & support as you approach full go-live.
Exam Traps
Change Enablement and Release Management are practices, not phases. Pilots and staged rollouts usually belong to the transition phase, not full operation.
Phase 5: Operation – Delivering and Supporting the Live Service
What is Operation?
Operation is where the live service runs and users consume it. Service management capabilities are applied daily to deliver outcomes and meet agreed levels.
Typical Operational Work
You handle incidents and requests, monitor performance and security, perform routine tasks, and communicate about outages and maintenance.
Value Chain Link
Operation maps mainly to Deliver & support in the service value chain, with some Engage and Improve for ongoing relationships and tuning.
Print Portal in Operation
Students log in and print, the service desk resolves issues, monitoring detects slowdowns, and IT applies driver and security updates regularly.
Exam Signal
Daily support, monitoring, and running the service according to service levels point to the operation phase and Deliver & support activity.
Phase 6: Continual Improvement – Feedback Loops Across the Lifecycle
Definition Reminder
Continual improvement is "A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations."
Improvement Everywhere
Improvement is not a final step. It happens in discovery, design, build, transition, and operation, at strategic, tactical, and operational levels.
Feedback Sources
You use feedback from user research, design reviews, build metrics, transition retrospectives, and operational monitoring to drive improvements.
Value Chain Activity
The Improve activity in the service value chain connects to any other activity and represents structured continual improvement work.
Exam Trap: Problem vs Improvement
Problem Management is a practice that supports improvement by removing causes of incidents. Continual improvement is broader and spans the whole system.
Thought Exercise: Map a Service You Use to Lifecycle Phases
Spend 3–4 minutes mapping a real digital service you use (for example, a music streaming app, online banking, or a learning platform like this one) to the lifecycle phases.
- Pick a service you know well.
- For each phase below, jot down 1–2 concrete examples. You can do this mentally or in a quick note.
- Discovery and demand shaping
- How do you think the provider discovered the need for this service?
- What user or customer problems does it solve?
- Design
- What design choices can you see in the interface, support options, or feature tiers?
- How do you think they balanced utility (what it does) and warranty (reliability, performance)?
- Build
- What kinds of components must have been built or configured (apps, APIs, integrations)?
- How might they test new features?
- Transition
- How do new features appear? Gradually, as beta options, or suddenly for all users?
- Have you ever seen a "new version" announcement or a staged rollout?
- Operation
- When something goes wrong, how do you get help?
- How does the provider communicate outages or maintenance?
- Continual improvement
- How do you see the service improving over time (new features, performance, fewer bugs)?
- Where might they be using your feedback or behavior data?
As a self-check, ask yourself: Which value chain activities and practices are most visible in each phase? This reflection will make the abstract ITIL terms feel more concrete and memorable.
Quiz 1: Identify the Lifecycle Phase
Test your ability to distinguish lifecycle phases from practices and value chain activities.
A team reviews user feedback and monitoring data from a live mobile app. They decide to simplify the login flow and schedule a small A/B test in the next sprint. Which lifecycle phase is MOST central in this scenario?
- Operation
- Continual improvement
- Design
- Change enablement
Show Answer
Answer: B) Continual improvement
The scenario is driven by learning from live use and planning targeted changes based on feedback and data. That is the essence of **continual improvement**, which is a recurring activity across all phases. Operation is involved (data comes from live use), and design work will happen, but the central idea is structured improvement. Change enablement is a practice, not a lifecycle phase.
Quiz 2: Lifecycle vs Value Chain vs Practices
Check that you can separate lifecycle phases from value chain activities and practices.
Which statement BEST describes the relationship between the digital product and service lifecycle and the service value chain in ITIL 4?
- The lifecycle replaces the service value chain in ITIL 4.
- Each lifecycle phase is a separate ITIL practice.
- The lifecycle is a time-based view that is realized through combinations of service value chain activities.
- The service value chain is only relevant during the operation phase.
Show Answer
Answer: C) The lifecycle is a time-based view that is realized through combinations of service value chain activities.
The lifecycle describes a time-based journey (discovery, design, build, transition, operation, improvement). The service value chain describes activities (Plan, Improve, Engage, Design & transition, Obtain/build, Deliver & support). Value streams combine these activities in different orders to realize the lifecycle phases. The lifecycle does not replace the value chain, and lifecycle phases are not practices.
Flashcards: Core ITIL Terms in the Lifecycle
Use these cards to reinforce key ITIL definitions that appear across lifecycle phases.
- service
- A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
- service value system
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- service value chain
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- service management
- A set of specialized organizational capabilities for enabling value for customers in the form of services.
- service offering
- A description of one or more services, designed to address the needs of a target consumer group.
- customer
- A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
- user
- A person who uses services.
- sponsor
- A person who authorizes budget for service consumption.
- utility
- The functionality offered by a product or service to meet a particular need.
- warranty
- Assurance that a product or service will meet agreed requirements.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
Pulling It Together: Lifecycle, Value Streams, and Exam Signals
Lifecycle as Storyline
The lifecycle is a storyline from idea to live service and back through improvement. Value streams built from value chain activities bring this storyline to life.
Example Value Stream
A feature flow: Engage/Plan (discovery) → Design & transition (design) → Obtain/build (build) → Deliver & support (release, run) → Improve (learn).
Recognizing Exam Patterns
Time sequence and journeys? Think lifecycle or value streams. Lists of Plan/Engage/etc.? Think service value chain. Named practices? Think capabilities.
Spotting Continual Improvement
If the scenario emphasizes ongoing learning, optimization, or recurring reviews, it is pointing to continual improvement and the Improve activity.
Next Steps in Skarp
Your upcoming diagnostics and mock exams will mix these layers. Practice quickly identifying lifecycle phase, value chain activities, and practices in each scenario.
Key Terms
- user
- A person who uses services.
- service
- A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
- sponsor
- A person who authorizes budget for service consumption.
- utility
- The functionality offered by a product or service to meet a particular need.
- customer
- A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
- warranty
- Assurance that a product or service will meet agreed requirements.
- value stream
- A specific combination and sequence of service value chain activities that creates value for a particular customer or stakeholder by delivering a product or service.
- lifecycle phase
- A stage in the time-based journey of a digital product or service, such as discovery, design, build, transition, operation, or improvement.
- service offering
- A description of one or more services, designed to address the needs of a target consumer group.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- service management
- A set of specialized organizational capabilities for enabling value for customers in the form of services.
- service value chain
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- service value system
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.