Value streams

Replacing what is often called "capability maps" and "process hierarchy" with something that ties directly to value creation

Introduction

Every process is a part of a value stream. A value stream is the flow of work that ends with a customer getting value, like order to delivery or idea to release. Value streams sit under the business model they serve, and they are made up of the processes that actually do the work.

If a process is not part of any value stream, it cannot exist without having to explain who it is for. Some processes exist to keep the company allowed to operate, like tax, audit and regulatory reporting. Those still belong to a value stream, with a clearly stated reason for it to exist.

The process graph

We choose to have all the processes in a graph rather than complicated hierarchies. The linear, hierarchical way of mapping processes often hits a very real friction point when it meets the real world.

A subprocess can be part of many processes, and a process can be part of many value streams. It is defined once, owned by its process lead and edited on its own page. Wherever it shows up, it is the same thing.

Example

A drone manufacturer makes its own motors. It uses some of them in the drones it sells to consumers, and sells the rest to other drone makers.

Every Monday, the planning lead decides how many of the week's motors go to the company's own drone line and how many go to B2B orders. That decision is one subprocess: allocating motor capacity. It is part of producing drones, and it is part of delivering motors to B2B customers.

In a hierarchy, it would have to be filed under one of them. If it sat under drone production, the B2B team would never see it, and the first time a big OEM order collided with a consumer launch, nobody would know why deliveries slipped. In the graph, both teams see the same subprocess, and when the planning lead changes how capacity is split, both value streams see the change at the same time.

Where things are measured

Flow is measured on the value stream: lead time, on-time delivery, flow efficiency. Work is changed in the processes. Initiatives change processes to move value stream measures.

Anything that has to stay healthy gets a defensive objective with measures and thresholds, whether it's a value stream, a process or a system. When a threshold is crossed, that is the reason to start an initiative.

Why not capability maps?

It's an abstraction that creates dishonest realities to fit into PowerPoints. A capability map groups work into boxes that don't follow how the work actually flows, so it drifts from reality the moment it is drawn. People mostly map capabilities because they trust the enterprise architect, not because the map helps them run anything.

What capability maps are used for is covered elsewhere. Health is covered by defensive objectives. Shared work is covered by subprocesses in the graph. Differentiation is decided in the business case, through how a process is run and the incentives around it, not by colouring a box.