SkarpChapter 10 of 20
Purposes of Lifecycle Activities: From Discover to Support
Dive deeper into each lifecycle activity, clarifying its purpose and common exam traps around where specific work really belongs.
The Lifecycle View Inside the Service Value System
Where This Fits
In this module you zoom in on the digital product and service lifecycle inside the ITIL service value system. You focus on what each lifecycle activity is for, how they connect, and where exam scenarios often try to trick you.
Exam Connection
The domain "The ITIL product and service lifecycle" expects you to recognize lifecycle activities and map tasks to the right place. These activities (discover, design, acquire, build, transition, operate, deliver, support) form value streams.
Key Definitions
Remember: a service is "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 management is the capabilities that enable this.
Link to Service Value Chain
The lifecycle activities mostly live inside the service value chain activities: "plan", "improve", "engage", "design and transition", "obtain/build", "deliver and support". You now make these abstract activities concrete.
Discover: From Signals to Opportunities
Purpose of Discover
The discover activity is about understanding opportunities, problems, and needs before you commit to a solution. It turns noise from the environment into focused insight for later lifecycle activities.
What Discover Does
Discover identifies and clarifies customer and user needs, understands PESTLE external factors, spots and prioritizes opportunities and problems, and feeds evidence to design instead of guesses.
Typical Discover Work
Examples: analysing incident trends, studying usage analytics for utility, interviewing customers, users, sponsors, and scanning new regulations or technology trends that might require new capabilities.
Exam Traps and Value
If a scenario is still clarifying the problem, it is discover, not design. Discover is continuous, not one-off. Its value is avoiding building the wrong thing and focusing on real improvements to value co-creation.
Design: Shaping Solutions with Utility and Warranty
Purpose of Design
After discover, design shapes a realistic solution. It translates needs into requirements and options, and decides how the service will provide utility and warranty across all four dimensions.
Utility and Warranty
utility is "The functionality offered by a product or service to meet a particular need." warranty is "Assurance that a product or service will meet agreed requirements." Design defines both for the future service.
Typical Design Work
Design activities include user journeys and mockups, non-functional requirements, sourcing decisions, architectures, SLAs, and defining how success and value realization will be measured.
Exam Traps and Value
If the scenario chooses features or SLAs, it is design, not discover. If it describes what the service should be (not building it yet), it is design, not build. Design balances utility and warranty to support value.
Acquire and Build: Getting and Creating the Components
Purpose of Acquire vs Build
Acquire obtains existing capabilities (like SaaS or hardware). Build creates or configures new components. Together they turn design specifications into real components that can be transitioned.
What Acquire Covers
Acquire includes purchasing or subscribing to SaaS, procuring hardware or cloud services, and contracting with partners and suppliers, ensuring they align with the designed service.
What Build Covers
Build includes coding, configuring off-the-shelf tools, creating automations and integrations, and performing unit tests so components meet the required utility and warranty.
Exam Distinctions and Link
Vendor selection and contracts point to acquire; coding and configuration point to build. Both mainly sit in the "obtain/build" value chain activity and depend on good design inputs.
Transition: Safely Moving into Live Use
Purpose of Transition
Transition moves new or changed services from build into live use in a controlled way. It focuses on risk-managed change and ensuring services are fit for live operation.
Typical Transition Work
Activities include release and deployment planning, formal testing, data migration, environment checks, and updating catalogues and knowledge so operations and support are ready.
Exam Traps
Unit tests by developers belong to build; acceptance testing and go-live checks belong to transition. If the goal is to introduce or change a service, think transition, not operate.
Value and Value Chain Link
Transition protects warranty by reducing deployment risk. It lives mainly in "design and transition", connecting obtain/build to deliver and support without harming existing services.
Operate and Deliver: Day-to-Day Value Realization
Operate vs Deliver
Operate and deliver sit mainly in "deliver and support". Operate runs the service day-to-day; deliver ensures outcomes actually reach customers in line with what was promised.
Operate: Running the Service
Operate includes monitoring infrastructure and applications, managing events and performance, and performing routine tasks like backups and capacity adjustments.
Deliver: Realizing Outcomes
Deliver focuses on executing value stream steps that turn service capabilities into outcomes, coordinating teams and suppliers, and ensuring SLAs and service promises are met.
Value Co-creation in Action
value co-creation is "The joint activities performed by a service provider and a service consumer to create value." Operate and deliver are where these joint activities happen in real time.
Support: Helping Users and Restoring Normal Service
Purpose of Support
Support helps users when things go wrong or when they need assistance. It restores normal service quickly, fulfils requests, and guides users in using services effectively.
Who Are Users?
A user is "A person who uses services." Support interacts directly with users through channels like chat, phone, and self-service portals, often via the service desk.
Typical Support Work
Support includes logging and resolving incidents, fulfilling standard requests, escalating when needed, and communicating about known errors, workarounds, and planned outages.
Exam Traps and Value
Operate is system-facing; support is user-facing. Support also feeds discover and improve with incident and request data. It protects user experience and trust during service issues.
Linkages Across the Lifecycle and Continual Improvement
Continual Improvement Defined
continual improvement is "A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations." It spans the whole lifecycle.
Key Linkages
Discover feeds design; design guides acquire/build; acquire/build supply transition; transition prepares operate/deliver/support; and operate/deliver/support generate data that restarts discover and improvement.
Improvement in Each Activity
You can improve how you discover needs, design patterns, build and source, deploy, and run and support services. Each lifecycle activity has its own improvement opportunities.
Exam Perspective
If a scenario is about learning from incidents or metrics and changing how work is done, it is about continual improvement as a cross-cutting activity, not a separate phase at the end.
Worked Scenario: Mapping Tasks to Lifecycle Activities
Scenario Overview
A university launches a new online exam booking service. You map each step in the story to the primary lifecycle activity, just like in an exam scenario.
From Discover to Build
Complaints and regulation review → discover. User journeys and requirements → design. Buying a scheduling platform → acquire. Configuring and integrating it → build.
From Transition to Support
End-to-end tests, training, migration, phased rollout → transition. Monitoring, capacity, backups → operate. Service desk helping students → support.
Improvement Loop
After the first season, analysing incidents and feedback to change booking rules and templates is continual improvement applied across discover, design, and support.
Thought Exercise: Classify the Work
Use this reflective exercise to strengthen your ability to map activities in exam scenarios.
For each description, pause and decide which lifecycle activity is primarily responsible: discover, design, acquire, build, transition, operate, deliver, or support. Some could involve several, but pick the best fit.
- A product manager runs a survey asking customers which mobile features they find hardest to use, then groups results into themes.
- A team defines recovery time objectives (RTO) and recovery point objectives (RPO) for a new payment service.
- An engineer implements infrastructure-as-code scripts to automatically create test environments.
- A vendor management specialist runs a request for proposal (RFP) to select a new data centre provider.
- The release manager coordinates a weekend deployment window and communicates expected downtime to stakeholders.
- An operations analyst tunes alert thresholds to reduce false alarms in monitoring tools.
- A service desk agent helps a user who cannot access the reporting dashboard and raises an incident.
- After a spike in similar incidents, a small team reviews root causes and updates standard change models to prevent recurrence.
When you are ready, compare your answers to the guidance on the next slide.
Suggested answers:
- Discover
- Design
- Build
- Acquire
- Transition
- Operate
- Support
- Continual improvement applied mainly to operate and support (but often categorized under improve in the service value chain).
Quick Check 1: Where Does This Work Belong?
Test your ability to identify the primary lifecycle activity from a short scenario.
A team is preparing a new analytics service. They have already chosen the vendor platform. Now they are defining data retention policies, access controls, and performance targets, and are mapping how users will navigate dashboards. Which lifecycle activity is primarily in focus?
- Discover
- Design
- Acquire
- Build
Show Answer
Answer: B) Design
The work describes specifying how the service should behave (data retention, access controls, performance targets, user journeys). That is the purpose of **design**. Discover would be about understanding needs; acquire was selecting the vendor; build would be implementing configurations or code.
Quick Check 2: Transition or Operate?
Distinguish transition from operate in a realistic situation.
An IT team performs a blue-green deployment of a new version of the customer portal, runs smoke tests, monitors closely for 48 hours, and has a rollback plan ready. Which lifecycle activity best describes this work?
- Build
- Transition
- Operate
- Support
Show Answer
Answer: B) Transition
This scenario is about moving a new version into live use in a controlled, low-risk way (blue-green deployment, smoke tests, rollback plan). That is the essence of **transition**. Operate would be the ongoing running after the change is accepted.
Flashcards: Purposes of Lifecycle Activities
Use these cards to reinforce the core purpose of each lifecycle activity and some cross-cutting ideas.
- Discover – core purpose
- Understand opportunities, problems, and needs by analysing data, feedback, and external factors so that later activities work on the right things.
- Design – core purpose
- Translate needs into requirements, architectures, and service designs that define utility and warranty across all four dimensions.
- Acquire – core purpose
- Obtain products, services, and capabilities from external or internal suppliers in line with the service design.
- Build – core purpose
- Create, configure, and integrate components so they meet design specifications and are ready for transition.
- Transition – core purpose
- Move new or changed services into live environments in a controlled, low-risk way, ensuring readiness of people, processes, and technology.
- Operate – core purpose
- Run and monitor services and underlying infrastructure day-to-day to meet agreed performance and reliability targets.
- Deliver – core purpose
- Coordinate and execute the activities that ensure service capabilities actually produce outcomes and value for customers.
- Support – core purpose
- Help users, resolve incidents and fulfil service requests, and protect the user experience while feeding insights into improvement.
- Continual improvement – definition
- "A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations."
- Value co-creation – definition
- "The joint activities performed by a service provider and a service consumer to create value." Operate, deliver, and support are where this is most visible.
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.
- 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.