SkarpChapter 10 of 19
Lifecycle in Practice: Linking Stakeholders, Value, and Improvement
Follow a concrete case study across lifecycle phases to see where customers, users, sponsors, and providers interact and where continual improvement fits in.
From Theory to Practice: Our Case Study and the Lifecycle
Our Case Study Service
We will follow a Student Support Portal (web + mobile) used at a university to submit tickets, track status, and access self-help knowledge.
Key Consumer Roles
Customer: Director of Student Services. Users: students and front-desk staff. Sponsor: Vice-Chancellor for Education who authorizes the budget.
Service Definition Reminder
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."
Lifecycle Phases
We will walk this service through: 1) Discover, 2) Design & Plan, 3) Build, 4) Transition, 5) Operate, 6) Improve (across all phases).
What You Will Track
In each phase we will map stakeholder touchpoints, value co-creation, and where continual improvement activities occur, plus exam-style traps.
Phase 1 – Discover: Who Wants What, and Why?
Discover Phase Focus
Discover = exploring needs and opportunities. ITIL 4 links this mainly to Engage and Plan value chain activities.
Stakeholder Needs
Users (students) report confusing channels. Customer wants faster responses and visibility. Sponsor cares about satisfaction, reputation, and cost.
Co-Creating Understanding
Workshops, interviews, and data analysis are value co-creation: provider and consumers jointly clarify what “better support” means.
Improvement Inputs
Past incident reviews and a continual improvement register feed lessons into the new portal’s requirements at this early stage.
Exam Pitfalls
Do not confuse customer with user, and do not assume value only appears at go-live. Value co-creation starts in Discover.
Phase 2 – Design & Plan: Utility, Warranty, and Value Alignment
Service Offering Design
Design & Plan turns needs into a service offering: a description of services tailored to the student support target group.
Utility vs Warranty
Utility = what the portal does (single form, tracking, knowledge base). Warranty = how well it does it (availability, speed, resolution times).
Stakeholder Roles Here
Customer signs off requirements and SLAs, sponsor approves budget, users help design journeys, vendor designs integrations and security.
Built-In Improvement
The team defines metrics and feedback loops (CSAT, surveys, reviews) so they can drive continual improvement after go-live.
Exam Tips
Do not separate utility and warranty; both are needed for value. SLAs are agreed with the customer, even if based on user input.
Case Walkthrough – Build & Transition with Stakeholder Touchpoints
Build & Transition Activities
The team configures the SaaS portal, integrates SSO, migrates tickets, creates knowledge articles, and trains support staff.
User Involvement
Students test the portal in a non-production environment. Their feedback simplifies categories and replaces jargon with clear labels.
Customer & Sponsor
Customer joins change meetings to time go-live; sponsor monitors progress and checks alignment with the business case.
Improvement During Build
Pilot releases let the team adapt quickly. Bigger ideas (like chatbots) go into the continual improvement register for later cycles.
Risks and Opportunities
Data migration errors are a risk; pilot analytics reveal opportunities, such as adding more Wi-Fi guides before launch.
Phase 4 – Operate: Daily Value Co-Creation and Service Management
Operate = Deliver & Support
In operation, students use the portal, agents resolve tickets, and supervisors manage queues. Service management is most visible here.
Service Management Reminder
Service management: "A set of specialized organizational capabilities for enabling value for customers in the form of services."
Stakeholders in Operation
Users use the portal and give feedback; the customer joins service reviews; the sponsor checks outcomes; provider teams run daily practices.
Co-Creation in Action
Students provide good ticket info and ratings; staff maintain knowledge; IT and vendor ensure performance. All co-create value.
Operational Improvement
Small tweaks, updated FAQs, and review-driven actions are continual improvement embedded in daily operations, not separate projects.
Continual Improvement Across the Lifecycle: Not a Final Phase
Definition to Remember
Continual improvement: "A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations."
Not Just an End Phase
Improvement appears in Discover, Design, Build, Transition, Operate, and between releases. It is woven throughout the lifecycle.
Case Touchpoints
In the portal case: past reviews shape Discover, metrics in Design, pilots in Build, tweaks in Operate, and structured cycles between releases.
Risks vs Opportunities
Risk: only fixing failures. Opportunity: using data and feedback to innovate and align with strategic goals like accessibility.
Exam Angle
Look for words like reviews, metrics, feedback, and small adjustments over time; these usually signal continual improvement concepts.
Map the Roles: Who Does What, When?
Use this thought exercise to solidify how customer, user, and sponsor appear across lifecycle phases.
Imagine the following four short scenes from our Student Support Portal case. For each, decide which role is most central and which lifecycle phase it most likely belongs to.
- Scene A: A senior leader reviews a business case showing expected impact on student satisfaction and approves a three-year budget for the portal.
- Question: Which role is this, and which phase are we in?
- Scene B: A group of students tries a prototype portal. They complain that the "Service Category" dropdown is confusing and suggest clearer wording.
- Question: Which role is this, and which phase are we in?
- Scene C: The Director of Student Services negotiates that high-priority tickets must be resolved within four business hours and insists on monthly performance reports.
- Question: Which role is this, and which phase are we in?
- Scene D: A student logs a ticket about exam timetable issues and later rates the support experience as 2/5 stars, adding comments.
- Question: Which role is this, and which phase are we in?
Pause and answer before checking the guide below.
Self-check guide (no peeking until you have tried):
- Scene A: Sponsor, mainly Design & Plan (budget approval) but influenced by Discover.
- Scene B: Users, in Build/Configure (prototype testing) or late Design.
- Scene C: Customer, in Design & Plan (requirements and SLAs).
- Scene D: User, in Operate (Deliver & Support) with feedback that feeds continual improvement.
If you mixed up customer and sponsor, review their canonical definitions again; this is a frequent exam distractor.
Quick Check 1 – Stakeholders and Value Co-Creation
Test your understanding of roles and value co-creation in the lifecycle.
An exam scenario describes a workshop where students, support staff, and IT meet to map current pain points and design a better support journey. Which ITIL 4 idea is BEST illustrated by this scene?
- Value co-creation
- Warranty
- Incident management
- Service continuity
Show Answer
Answer: A) Value co-creation
The scene shows provider and consumers jointly shaping the service, which matches **value co-creation**: "The joint activities performed by a service provider and a service consumer to create value." Warranty is about assurance that requirements will be met, incident management is about restoring normal service after disruptions, and service continuity is about major disruption and disaster planning.
Quick Check 2 – Continual Improvement in Context
See if you can spot where continual improvement is happening.
The service desk team notices that 30% of tickets are misrouted because students pick the wrong category. They adjust the category names and add short descriptions, then monitor the effect the following month. Which statement BEST describes this activity?
- A one-time design change that ends the lifecycle
- An example of continual improvement during operation
- A budgeting decision made by the sponsor
- A change that only affects warranty, not utility
Show Answer
Answer: B) An example of continual improvement during operation
This is a small, data-driven tweak made during daily operations, then checked later. That matches **continual improvement** during the Operate phase. It is not the end of the lifecycle, not a budgeting decision, and it affects both utility (easier to use) and warranty (fewer delays and errors).
Key Terms and Definitions – Lifecycle and Stakeholders
Flip these cards mentally to reinforce the exact wording of key ITIL 4 terms that appear in lifecycle questions.
- 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.
- 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.
- service offering
- A description of one or more services, designed to address the needs of a target consumer group.
- 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.
- 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.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
Exam-Focused Wrap-Up: Reading Lifecycle Scenarios
Reading Lifecycle Scenarios
Identify the phase from what is happening: Discover, Design, Build, Operate, or Improve. Exams describe actions, not labels.
Roles by Decisions
Customer defines requirements and outcomes; user interacts with the service; sponsor approves budget. Focus on what the person does.
Signals of Co-Creation
Words like co-design, workshops, and feedback shaping the service usually mean value co-creation is being tested.
Patterns of Improvement
Recurring reviews, metrics analysis, and logged ideas point to continual improvement, which overlays all lifecycle phases.
Next Step in Skarp
Use the diagnostic quiz and upcoming mock exam to test your ability to map scenarios to phases, roles, and ITIL concepts accurately.
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.