The ITIL® Product and Service Lifecycle Explained (ITIL® 5)

What Is the ITIL® Product and Service Lifecycle?

The ITIL® Product and Service Lifecycle Model (often shortened to PSLM) is the central model ITIL® 5 uses to describe how a digital product or service moves from an idea to something customers actually use and rely on. It's built around eight activities: Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support.

Earlier versions of ITIL® treated product creation and service management as two separate worlds, often with different teams, different tools, and different ways of thinking. ITIL® 5 brings them together into one shared lifecycle, on the reasoning that a product and the service built around it are really two perspectives on the same underlying solution.

Not a Straight Line — An Ecosystem

The biggest mental shift is that this lifecycle is not meant to be read left to right like a waterfall process. It's explicitly described as non-linear and non-prescriptive: any activity can move backward or forward to any other activity, and a single product or service can have different versions sitting in different stages at the same time.

That means a team might be operating one version of a service while simultaneously discovering requirements for the next one, or looping back from Build to Design after testing reveals a gap. The model is meant to reflect how digital work actually happens — messier and more iterative than a strict sequence.

The Eight Lifecycle Activities

The earlier activities lean toward Product thinking — creating something. The later activities lean toward Service thinking — running and supporting something for customers. Transition and Operate sit in the middle, acting as the bridge between the two.

Real-World Example

A company decides to replace its manual expense-approval spreadsheet with a proper internal app. Discover starts with talking to finance staff and managers about what's actually slowing them down. Design turns that into a specification and a clickable prototype. Acquire brings in a small development team and a cloud hosting plan. Build is the actual coding and testing of the app.

Transition moves the finished app from a test environment into production. Operate keeps it running reliably day to day. Deliver makes sure employees across the company can actually access and use it, not just that it technically exists. Support fields the inevitable "I can't submit my expense report" tickets once real people start using it — and issues raised through Support often loop straight back into a fresh round of Discover for the next improvement.

Why This Matters

Understanding the Product and Service Lifecycle matters because:

• It explains why ITIL® 5 talks about "products and services" together instead of treating them as separate disciplines
• It clarifies that the lifecycle is iterative, not a rigid sequence you complete once
• It gives you a shared vocabulary for where a piece of work sits at any given moment — whether it's still being discovered, actively being supported, or somewhere in between

Common Exam Mistakes

The most common mistake is treating the eight activities as a strict, one-directional pipeline — Discover always happens first, Support always happens last, full stop. In reality, the model explicitly allows movement in any direction, and every activity can trigger fresh discovery.

A second mistake is assuming the Product and Service Lifecycle is just a renamed Service Value Chain. It's a genuinely different model — it merges product and service management into one lifecycle, rather than describing a chain of value-creating activities within service management alone.

Memory Trick

Think:

Discover, Design, Acquire, Build — that's building the thing.

Transition, Operate — that's the bridge.

Deliver, Support — that's living with the thing.

Nothing about the order is fixed — think ecosystem, not assembly line.

Key Takeaways

• The ITIL® Product and Service Lifecycle has eight activities: Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support.
• It replaces the Service Value Chain from ITIL® 4 and unifies product management and service management into one lifecycle.
• The model is non-linear — any activity can move to any other activity, and multiple versions of a product or service can exist in different stages at once.
• Earlier activities lean toward Product, later activities lean toward Service, with Transition and Operate acting as the bridge.
• This is one of the most structurally significant changes in ITIL® 5 and a frequently tested area of the Foundation syllabus.

One Practice Question