Business Process Expert·8 min read
The fastest way to understand value stream mapping is to read a few real ones. Each example below shows the process steps, the actual work time at each step, and the waiting between them - then unpacks what the map is telling you. If you are new to the method, start with the value stream mapping overview first.
Watch for the same pattern in all four: the value-add time is tiny, and the lead time is enormous. The gap between them is the whole point.
1. Manufacturing: a machined-part order
A build-to-order shop receives a customer order and delivers a finished machined part. This is the classic value stream Toyota first mapped.
Order entry
Engineering
Machining
Assembly
Ship
Lead time ~11 days · Value-add ~1.9 hrs
What the numbers reveal
The work takes under two hours, but the customer waits eleven days. Almost all the delay is queue time between departments - not slow machining. The lever is flow: smaller batches and a pull signal between engineering and machining, not a faster CNC.
2. Software delivery: a feature from request to release
A DevOps team moves a feature from backlog to production. The "material" is code; the "information" is tickets and reviews.
Refine ticket
Develop
Code review
QA test
Deploy
Lead time ~12.5 days · Value-add ~2.6 days
What the numbers reveal
Development itself is efficient. The waste sits in the waits before code review and QA - work finished but sitting in a queue for a busy reviewer or a batched release window. Continuous review and smaller, more frequent deploys collapse those queues far more than hiring faster developers would.
3. Healthcare: an outpatient clinic visit
A patient flows from arrival to discharge in an outpatient clinic. Value-add is time a clinician spends on the patient; everything else is waiting rooms.
Check-in
Triage
Physician
Labs
Discharge
Lead time ~3.3 hrs · Value-add ~43 min
What the numbers reveal
The patient spends over three hours in the clinic for 43 minutes of care. The waiting rooms are the value stream problem. Level-loading appointment slots and running triage and labs in parallel with physician availability cut the total visit without adding a single clinician.
4. Procure-to-pay: an invoice from receipt to payment
A finance team processes a supplier invoice from arrival to payment - a back-office value stream where the "product" is an approved payment.
Receive invoice
Match to PO
Approve
Schedule pay
Pay
Lead time ~15 days · Value-add ~26 min
What the numbers reveal
Twenty-six minutes of work stretched across fifteen days. The approval wait is the giant - invoices sit in an inbox waiting for a manager. This is a textbook automation target: auto-match invoices to purchase orders and route approvals by rule, and the fifteen days can drop to two.
"Notice that across four completely different industries, the diagnosis is nearly identical: the work is fast, the waiting is slow, and the fix is flow - not effort. That is why value stream mapping travels so well. Once you can read one map, you can read them all."
Turn the map into a decision
In the procure-to-pay example, the approval wait screamed "automate me." Once your value stream is visible, you can decide which steps to make AI-assisted or automated and use the mapped numbers as your before-and-after baseline. In Crismo you can map the value stream and tie a process diagram to each step with value streams.
Keep learning
Frequently asked questions
What is a good example of a value stream?▼
Any end-to-end flow that delivers something to a customer: an order becoming a shipped part, a request becoming a released feature, a patient arriving and being discharged, or an invoice becoming a payment. If work flows through steps to reach a customer, it is a value stream.
Can value stream mapping be used outside manufacturing?▼
Yes. Software, healthcare, and finance examples all follow the same structure. The technique maps any flow of work, whether the "material" is a physical part, a line of code, a patient, or an invoice.
Why is the value-add time so much smaller than the lead time?▼
Because work spends most of its life waiting in queues, not being worked on. That is the recurring insight in every example - and the reason VSM focuses attention on removing waits rather than speeding up steps.
What should I measure for each step?▼
At minimum, the processing (work) time and the waiting time before the step. Add cycle time, changeover time, and percent complete-and-accurate where they matter to your stream.
How many steps should an example VSM have?▼
Keep it to the major stages - usually five to ten process boxes. Too much detail turns a value stream map into a process map and hides the flow picture you are trying to see.
Model your value stream in Crismo
Crismo lets you map value streams and tie a detailed BPMN process diagram to each step, connecting strategy to execution. It links processes to the flow rather than using the classic Lean VSM symbols.
See value streams in Crismo