Two Altitudes: Value Streams and the Process Maps Beneath Them

Crismo Team — Thu, 13 Aug 2026 22:06:48 +0000

If you've ever argued about whether your team should be doing value stream mapping or process mapping, you're asking the wrong question. They aren't competitors. They're two altitudes of the same operating model — and the real leverage comes from connecting them.

Here's the distinction in one line:

Value stream mapping shows the strategic flow of an entire product or service and where time is wasted. Process mapping shows the detailed execution of a single process and exactly how each step runs.

VSM answers what to improve. Process mapping answers how the work is actually done. You need both.

The high altitude: the value stream

A value stream is the business-oriented, end-to-end view — a handful of segments anyone in the organization can orient around. Think demand to delivery, order management, lead to cash. Kept at this altitude, the value stream is a strategic instrument: it shows where lead time and inventory pile up between steps, which is exactly where most of the waste hides.

The classic Lean VSM notation — process boxes, data boxes, inventory triangles, the timeline ladder with its lead-time vs. value-added split — exists to make that waste impossible to miss. A single number, the ratio of value-added time to total lead time, usually tells the whole story. (Spoiler: it's almost always shockingly low.)

The low altitude: the process map

Drop into any one of those segments and you hit the process layer. This is where a formal notation like BPMN earns its keep: precise steps, decisions, roles, handoffs, and exceptions. A process map is what you standardize, train against, audit, and automate. It's too detailed to run a strategy conversation on — and that's the point. Different altitude, different job.

For the full side-by-side, see value stream mapping vs process mapping.

The real move: link the two altitudes

Most organizations have both — a value stream slide somewhere and a pile of process diagrams somewhere else — and no connection between them. That gap is where process programs quietly die.

The fix is to interlink them deliberately, in two directions:

Vertically — each value-stream segment links down to the detailed process map(s) that implement it. Stream → segment → process. You can start at the strategy and drill into the execution without leaving the map.
Horizontally — each segment hands off to the next, so you can follow the end-to-end path across the business, not just admire it as a static picture.

Do this across the organization and a pile of disconnected diagrams becomes a navigable landscape — an operating model you can actually traverse. That structure is what turns seeing the waste into changing it: you spot the slow segment on the stream, drop into the process map, and redesign it with a clean as-is vs to-be comparison. The value stream told you where; the process map lets you fix the how.

Why this matters more in 2026

There's a second payoff to a linked landscape: it's the highest-quality context you can hand an AI. A single diagram is a picture. An interlinked value-stream-to-process landscape is a graph of how your business actually operates — which segment feeds which, what each step costs, where the queues form. That's the difference between asking an AI to "optimize a diagram" and giving it the operational context to reason about a real end-to-end flow.

You don't get that from a value stream map alone, and you don't get it from a pile of orphaned process diagrams. You get it from linking the two altitudes.

Where to start

Sketch the value stream at the top: 5–9 business segments, no more.
For each segment, link the process map that implements it (or note that one's missing — that gap is itself a finding).
Add the horizontal handoffs so the end-to-end path is walkable.
Only then go deep on the segment with the worst lead-time ratio.

Keep the stream strategic. Push the step-by-step detail into the process layer beneath it. The value is in the link.