AI Along Your Value Streams: A Practical Map

When leaders ask how to use AI, the question usually arrives as a tool question: which assistant, which platform, which vendor. That framing skips the more useful step. The place to start is the work itself, the chain of activities that turns an input into a result a customer values. This chain is a value stream.

A value stream runs end to end. Procure-to-Pay runs from a purchase requirement to a paid invoice. Issue-to-Resolution runs from a customer raising a problem to that problem being solved. Once the stream is explicit, the question changes from “which tool” to “which step, and how far should AI take it”. That is a question you can answer with evidence. The examples in this series are kept deliberately simple. Real value streams are usually far more complex, with many more steps, systems and hand-offs, and mapping them is what makes that complexity workable.

We always look at the whole stream from end to end and that is deliberate. Value reaches the customer only when the whole chain delivers, so a faster single step helps nobody if the work then waits at the next hand-off. Most delay and most error sit in the hand-offs between steps rather than inside them, and automating one step on its own often just moves the bottleneck along. Looking at the whole stream is what lets us judge whether a change really shortens delivery or only looks impressive in one place.

For each step we distinguish four levels of how deeply AI is involved. These levels are the backbone of the whole series.

Classical: people do the work by hand. AI is not involved.

Assistive: a person does the work and AI suggests. The human keeps every decision.

Agentic: AI performs a bounded step on its own, and a human reviews and approves the result before it counts.

Autonomous: AI runs the step without case-by-case approval. A human monitors the system and sets the guardrails.

The pattern across the levels matters more than any single level. As AI takes over more of the execution, the human role moves from doing the work to specifying, reviewing and governing it. The human keeps control, only now at the gate rather than at the task. Each step up trades more of the routine work for more control and integration effort. For a business case that trade matters more than the label on the level.

For most organisations, and especially cautious or regulated ones, the realistic target is agentic with a human gate: the AI does the bounded work and a person still approves it before it counts. Full autonomy stays rare and situational.

Each step up has its own price of entry. Moving from classical to assistive is mostly a matter of access: digitized processes and data, a capable AI model, plus people trained to use its output and to judge it. Moving to agentic asks for a foundation: a solid data foundation in integrated systems or a data warehouse, API access so the AI can act rather than only suggest, plus a bounded process with a clear success criterion and a review gate. Moving to autonomous is the highest bar: reliable IT infrastructure with monitoring, a mature and largely automated process, plus strong data governance and guardrails with a human fallback. The infrastructure builds up and carries forward, while the control points are added level by level. The concrete threshold still depends on the stream, so we mark what each step up requires on the maturity view and show, on the real cases, what an organisation actually had in place before it moved.

There is also a second price, and it is easy to miss. The deeper you integrate AI, the more of your own knowledge you have to hand it to make it useful, so proprietary data and context become part of the cost, not only the licence fees. How much that matters depends on how you run the model. On public consumer tools your inputs can feed the provider's training, while on enterprise and API tiers with zero data retention, or in a private or on-premise deployment, they stay on your own instance and are not used to train the model. For a regulated organisation that containment choice belongs in the plan from the start, right next to the value case.

We describe an enterprise with ten value streams. Together they cover almost every part of a company.

They fall into three groups: the core value chain that creates and delivers the product, the planning that steers it and the supporting functions that keep it running. The table below names each stream and what it does.

This map is the reason the series works as a directory. A company can point to any part of its operating model and find the matching stream, then read how AI changes it. Open the interactive map and walk into any stream: the value-stream map.

Every stream in the series is described the same way. That consistency is deliberate: it lets you compare one stream against another and trust that the same questions were asked. Two sets of dimensions do the work.

The first set describes the structure of the stream. For each of the four maturity levels we lay out the steps and how they change: which steps merge, which shift, which appear. On top of that sits a profile of the whole stream: its primary goal, the typical performance indicators, the prerequisites for the agentic and autonomous levels and how the work splits between people and AI. A short assessment of strengths, weaknesses, opportunities and threats rounds it out.

Idea-to-Market is a worked example. The figure below lays the stream out across the four levels, so you can see the steps merge and shift as AI takes on more: the Idea-to-Market stream.

The second set describes each real-world case. When we cite an example, we record the same fields every time: the reported metric, where a human reviews or approves, the control gates, how much the result depends on context, the risks and lessons and the source. We include only cases we could verify against a credible source, and every case carries a reality-check: where the number does not transfer, and what breaks outside ideal conditions.

A framework is only worth as much as the evidence behind it, so we keep the evidence in plain sight. As the series works through the streams, the real cases add up into a library you can actually browse. Every case is written the same way: a quick picture of how the AI sits inside the work, what it changed, the number that was reported and, just as important, the point where that number stops holding.

Think of the map below as the table of contents. Each case sits under the value stream it belongs to, the cross-cutting studies keep a column of their own and the whole thing grows with every post. Click a tile and it opens into the full entry: the case library.

Take Amazon Q. Behind that tile is one case, laid out the way all of them are: the claim, the human who signs it off, the honest limit and the source you can open and check yourself: the Amazon Q case.

New cases are added over time, each tied to the level of AI integration it shows and each with its positive and negative sides. Together they build a comprehensive picture and give real examples of what AI could mean for your own company, while keeping one thing in view: a full plunge into the deep end of the AI pool is not for every company or industry.

The rest of the series takes the streams one at a time. Each post walks a single value stream through the four levels and shows the real cases with their honest limits, so you can see how far AI can go in that stream, from a careful first step to a fully agentic setup. Next up is Idea-to-Market.

Want to see it? The two worked streams are live to explore: walk Idea-to-Market through the four levels and open any case in the library to check the evidence yourself: explore the streams on Metapad.

Want to do this on your own value streams? That is exactly what our AI-Driven Operating Model Workshop is for: the same method applied to your real value streams and your people, ending with a map of where AI fits, what is realistic at each step and what to try first.