Your new workforce won't be all human. Join the
conference to learn the new workforce OS.
request invite
TL;DR: The ITIL 4 service value chain has six activities: Plan, Improve, Engage, Design and Transition, Obtain/Build, and Deliver and Support. They combine into value streams that turn demand into value. The model is sound; the manual glue between the activities is the bottleneck. Generative AI and agentic AI, running as a governed, read-only AI Coworker, can do that connective work inside each activity (gather evidence, correlate systems, draft the report, route the ticket) under human control, while a person keeps the decisions. This post walks the six activities and maps each to a real run.
If you run IT with ITIL 4, you already think in terms of the service value chain. It is the operating model at the center of the service value system: six activities that take demand and opportunity in, and produce value out. The activities are flexible on purpose, you combine them into value streams for different kinds of work, from a new laptop request to a major incident.
Part of the ITIL 4 series: The seven ITIL 4 guiding principles, Focus on value, the first guiding principle, Start where you are, the second guiding principle, Progress iteratively with feedback, the third guiding principle.
The framework is not the bottleneck. The bottleneck is that the glue between the activities is manual. Someone has to pull the data, reconcile three systems, write the summary, and move the ticket forward. That is exactly the work a governed AI Coworker is good at: read the evidence, reason over it, draft the output, and stop at the point where a human should decide. ITIL 4 even names the instinct in its guiding principles: optimize and automate, and collaborate and promote visibility.
Below, each of the six activities, in plain terms, and what it looks like when a Coworker does the connective work. For a fuller primer on the framework itself, Atomicwork has a good ITIL 4 guide.
Plan is about direction: strategy, policies, and the portfolio, keeping everything pointed at business value. In practice, planning stalls because the numbers are scattered and a week out of date by the time someone assembles them.
A Coworker turns "I need a view" into a view. Instead of a six-week BI project, it reads the live service-desk data and assembles the dashboard a leader actually asked for, and it flags the numbers it cannot verify rather than faking them. Planning a change is a decision too, and change intelligence scores blast radius from the CMDB before the CAB meeting, so the plan is informed rather than guessed.
Improve is continual improvement across every service, practice, and piece of data. It depends on knowing the current state honestly, which is where most improvement efforts quietly fail: the CMDB is wrong, the knowledge base is stale, and nobody measures the right thing.
A read-only Coworker is well suited to surfacing decay. It audits the CMDB against the real sources of truth and shows the drift instead of trusting the record (your CMDB is lying to you). And improvement shows up as measurable outcomes, like the first ten minutes of an incident handled before a human joins, in how an AI SRE cut MTTR.
Engage is every interaction with users, customers, and stakeholders: understanding demand, taking requests, setting expectations. It is where experience is won or lost, and where rule-based automation tends to break.
The honest version of engagement is resolving the request, not just deflecting it. Rule-based triage turns every helpdesk into a workflow-automation black hole; a Coworker reasons over the actual ticket instead. And engagement can flow straight into fulfillment: an engineer asks in Slack for a cloud server and a guardrailed Coworker takes it from request to provisioned, inside policy.
Design and transition covers designing new or changed services and moving them into live use safely: change enablement, release, the parts where good intentions cause outages.
This is where guardrails matter most, because the risky step is changing what ships. Approved changes still cause outages when risk is guessed rather than analyzed, and generative AI reading the CMDB can score that risk before approval. When a Coworker debugs a broken build, it can find the exact line and write the fix, then refuse to merge it without human approval.
Obtain/build is acquiring or building the components a service needs: procurement, provisioning, development, licensing.
A Coworker helps here by executing within policy, never holding the keys itself. Guardrailed GCP VM provisioning runs the build through a credentialed gateway with every step logged as ticket evidence. Obtaining also means obtaining within budget, which is why a FinOps Coworker that catches a cloud bill jumping overnight belongs here: it traces the spend to the resource that changed and proposes the fix without touching the account.
Deliver and support is ongoing delivery and the support that keeps services running: incidents, requests, access, operations. It is the busiest part of the value chain and where a Coworker earns its place fastest.
Incidents are the clearest case: agentic major incident management, an on-call AI buddy that opens a triaged war room before the engineer is online, and a disaster-recovery flow from alert to war room in under a minute. Support also means governance work that never gets done: a quarterly access review, endpoint compliance audits, certificate expiry monitoring, and shadow AI detection across the workspace. Under all of it sits an accurate self-updating asset inventory, because delivery and support quietly ride on knowing what you have.
ITIL 4 wraps the value chain in a service value system that includes governance for a reason. If you are going to let software act inside your value chain, the governance has to be explicit, and it is the same pattern in every example above: the Coworker is read-only by default, it does the work that carries no downside (read, correlate, draft, recommend), and it stops at the step that needs a human, changing production, revoking access, merging code. Autonomy up to the line, a hard stop at the line, and every step logged as evidence.
What is the ITIL 4 service value chain? It is the central operating model of ITIL 4: a set of six activities that take demand and opportunity as input and produce value as output. The activities are combined into value streams tailored to different kinds of work.
What are the six service value chain activities? Plan, Improve, Engage, Design and Transition, Obtain/Build, and Deliver and Support. They are not a fixed sequence; you arrange them into value streams as the work requires.
Where does AI fit in the value chain? Inside each activity, doing the connective work that is currently manual: gathering evidence, correlating systems, drafting reports, routing tickets, and recommending actions. The decisions, and any change that carries risk, stay with people.
Does an AI Coworker replace ITIL practices? No. The practices and the value chain stay as they are. A Coworker is a way to perform the low-value glue faster and more consistently within them, under human control.
How do generative AI and agentic AI align with ITIL 4? They align at the level of the service value chain and the guiding principles. Generative AI drafts, summarizes, and explains; agentic AI takes multi-step action across systems. The guiding principle it maps to most directly is optimize and automate.
Is this an official ITIL product? No. ITIL 4 is owned by AXELOS and PeopleCert. This post explains the value chain in our own words and maps it to how we use AI Coworkers; it is not affiliated with or endorsed by AXELOS or PeopleCert.
The ITIL 4 service value chain is a good model, and it does not need replacing. What it needs is for the manual glue inside each activity to get faster without losing control. A governed, read-only AI Coworker does exactly that: it reads, correlates, drafts, and recommends across Plan, Improve, Engage, Design and Transition, Obtain/Build, and Deliver and Support, and it hands every real decision back to a human. The value chain stays the same. The time-to-value gets shorter.
See how AI Coworkers work across the service value chain at atomicwork.com.
Sources and further reading: Atomicwork ITIL 4 guide; PeopleCert ITIL 4 Foundation; AXELOS ITIL service management.
