ZBTOS by ETEGY
Ten questions · 5 minutesTransformation Lens Check →

Value Streams vs. Process Maps

Mapping work? Choose the view that can show what you need to see.

ForPractitionersBusiness architectsProcess owners
A team comparing how work moves across their functions
Process map.
How a step is done.
Workflow.
The sequence work follows.
Value stream.
Whether value arrives at the end.
EXHIBIT 1 · THE SAME WORK, TWO VIEWS
FULFILLMENT TEAM · PICK, PACK AND SHIP
Pick list received
Pick items
Pack order
Quality
check
Ship
Shipment confirmed
↺ Fail: back to Pack order
Steps
6, all inside one team
Cycle time
Measured per step
Improves
How each step is done
A good process map: every step inside one team’s scope, ready to be improved. It cannot show what happens before the pick list arrives or after the shipment leaves.
Why it is no longer optional
The redesign starts next month. Are you mapping the view that can show the problem?

Most value is lost between teams, at the handoffs. A map drawn inside one scope improves the steps and leaves the flow between them untouched.Only 35% of companies achieve their digital transformation objectives.BCG, Performance and Innovation Are the Rewards of Digital Transformation (2021), 850+ companies

The three views

Three views of the same work

Process maps, workflows and value streams all describe work, and the terms are often used interchangeably. They are not the same. A process map shows the steps inside one scope. A workflow shows the route one item takes through tasks and systems. A value stream follows a request from the moment it enters the business to the moment its value is proven, across every team it passes through.

The difference is width. A process map can be complete and correct for one team and say nothing about what happens when the work leaves that team.

Each view answers a different question. Pick the one that can show the problem.

Two different questions.

Process maps and workflows ask
How is this step done? What sequence does this item follow? Where is this team slow?
A value stream asks
Where does demand enter, and is it governed? Where does work lose value between teams? Is the value proven at the end?
Day one

What your team can do after training.

Foundation teaches the method on the Meridian case, with each area applying it to its own work. Practitioner Intensive applies it to one live transformation.

01Foundation
Choose the view.
Distinguish value streams, workflows and process maps. Know which view answers which business question.
02Foundation
Bound the stream.
Using the Meridian case, identify where the value stream begins and ends, its contributing functions and its critical handoffs.
03Foundation
Find the suspect handoff.
Identify where work stalls, is re-keyed or loses its governing record, and what evidence would establish the loss.
04Intensive
Direct the process work.
On one live transformation, identify which handoffs warrant deeper mapping or redesign and what the responsible teams need to examine.
A new way to use the training
Train before the tool.

Run the Foundation Course ahead of a process-mining or automation rollout, so the tool is pointed at the stream that matters, not at every process it can find.

Outcome: Start with the value stream, not the process map. Identify which handoffs matter before committing effort to detailed mapping, automation or redesign. Learned through the Meridian case in Foundation; applied to one live transformation in the Practitioner Intensive.

Questions

Which one should a transformation start with?

The value stream. It shows where value is lost between teams, which is where most transformation problems sit. Process maps and workflows come later, inside the lanes that need to change.

Can a value stream be drawn with process-mapping tools?

Yes. The tool matters less than the question. A value stream asks whether work survives each handoff and whether its value is proven at the end.

Where does ZBTOS teach this?

In the Foundation Course, where a cohort maps a shared case on the GSDPI™ Lifecycle Map and sees the difference in practice.

Guide · free
Read work the way value moves.
Read the Introduction to Zero-Based Transformation™ →Learn to read value streams: Foundation Course ›

Not ready for a course? Get the ZBTOS Briefing › New reads on choosing the right view of the work.

ZBTOS by ETEGY

Training, assessment and support for transformation capability.

Carrying an external mandate? ETEGY →
Zero-Based Transformation™, ZBTOS™, GSDPI™, Voice of the System™ and Traceability Ratio™ are trademarks of ETEGY. Get. Sort. Do. Prove. Improve.® is a registered trademark of ETEGY. Privacy · © 2026 ETEGY