Deliver
Stage 7 in the Lifecycle
Deliver is where services reach users under agreed commitments. It differs from Operate, which maintains product health -- Deliver executes service actions and access defined with customers and users.
What you should take away
- State the official purpose of deliver
- Explain how SLAs frame deliver work
- Describe the three relationship types (access to resources, service actions, transfer of goods)
- List the three workflow steps and common triggers for new deliver iterations
Official purpose
"The purpose of deliver is to provide services to users, manage user onboarding and offboarding, maintain service quality standards, and gather consumer feedback."
Operational products form the foundation. Operate maintains the product; Deliver fulfills what Service Level Agreements promise.
Key facts
| Question | Answer |
|---|---|
| Why do it? | Provide services, manage onboarding/offboarding, maintain quality standards, gather feedback |
| Who does it? | Service delivery teams, user support teams, service desk teams |
| When performed? | Continually, triggered by SLA changes, service events, and requests |
| Key outputs? | Delivered services, performance records, user feedback reports |
| Success metrics? | Customer/user satisfaction, SLA achievement, adherence to strategy, stakeholder satisfaction |
Service relationships (what Deliver includes)
Deliver involves three types of relationships:
- Access to resources (equipment, apps, data, knowledge, support channels)
- Transfer of goods (kits, keys, manuals, consumables)
- Service actions (training, support, reporting, logistics activities)
Scope depends on product architecture, service offering, and agreements.
High-level workflow (three steps)
Assess service delivery commitments and available solutions
Identify and confirm the delivery plan and resource availability
Execute delivery plans; report delivery status to stakeholders
Triggers for deliver iterations
New iterations are triggered by:
- SLA changes (including new SLAs)
- Service requests under existing SLAs
- Service events defined in SLAs (actions that run without user request)
Service request (definition)
"A service request is a user or authorized representative request that starts a normal, pre-agreed part of service delivery."
Scope variation
Complexity ranges widely. App-based products may need only access and satisfaction monitoring. Corporate services may require fulfillment teams for requests, onboarding, and ongoing actions. When only access exists, deliver focuses on status and satisfaction monitoring.
Extended delivery topics
Service level and catalog
- SLA monitoring and review
- Catalog and self-service
Experience (ITIL v5 emphasis)
- Customer, user, and employee experience
- XLAs as extensions of classic SLAs
Related management practices
| Practice | Role in Deliver |
|---|---|
| Service Level Management | Targets and reporting |
| Service Request Management | Fulfill requests |
| Relationship Management | Stakeholder engagement |
| Service Financial Management | Cost and value dialogue |
| Measurement and Reporting | Evidence of performance |
Inputs and outputs
Inputs: Live product, SLAs, expectations, financial guardrails
Outputs: Delivered services, performance and feedback records, incidents for support, improvements for discover and design
Metrics (examples)
- SLA achievement
- CSAT, NPS, XLA-style scores where used
- Cost per service unit
- Value or outcome indicators agreed with customer
ITIL Car Rental scenario: Deliver in action
The autonomous vehicle service team monitored satisfaction scores (4.95 rating), analyzed delivery data showing local vs. out-of-town user patterns, and used negative feedback to drive improvements like AI scanning for vehicle conditions and adjusted discount policies.