This value stream map template keeps material movement, information signals, and elapsed-time intervals together. The worked example follows one invitation pack from order receipt to dispatch-ready, then compares one explicitly proposed waiting-time change.
Define the product family and the time boundary
The original fictional product is a folded invitation pack. The teaching boundary starts when its order is received and ends when the pack is dispatch-ready. Shipping after that point is excluded. The supplied times are invented model inputs, not observations from a workshop or a promise about production.
Lean Enterprise Institute's value-stream-mapping definition emphasizes the whole product-family flow, including material and information, and distinguishes current conditions from a proposed future state. A map can expose connections that a diagram of one operation misses.
Use the same item and boundary when comparing time. The intervals below are serial and do not overlap. Their sum describes one modeled pack's elapsed time; it is not a throughput rate, a machine cycle-time measurement, or a staffing estimate.
Read all six intervals
| Interval | Supplied duration | Role in the current teaching model |
|---|---|---|
| W1 · Wait before printing | 60 minutes | Order waits for the initial release. |
| P1 · Print | 12 minutes | Printing work on the pack. |
| W2 · Wait before folding | 120 minutes | Printed material waits for the batch-release arrangement. |
| P2 · Fold | 8 minutes | Folding work on the pack. |
| W3 · Wait before packing | 42 minutes | Folded material waits for packing. |
| P3 · Pack | 18 minutes | Packing work until dispatch-ready. |
The processing intervals total 12 + 8 + 18 = 38 minutes. Waiting totals 60 + 120 + 42 = 222 minutes. Together, they give 38 + 222 = 260 minutes within the stated boundary.
Keep those totals attached to the interval definitions. Do not add a separate whole-stream lead time to the six intervals; that would count the same elapsed time again. If operations overlap in your actual process, this serial addition model needs to change.
The map separates processing from waiting. It does not automatically declare every processing minute value-adding or every wait avoidable. Those judgments need the actual customer and process context.
Show what tells the work to move
The material path is print → fold → pack. The information path is order record → planner release → production instructions for the operations. A release instruction communicates permission or timing under the modeled process; it does not itself move the material.
Choose Planner release in the example to inspect the information signal beside W2. The current teaching model associates that 120-minute queue with its batch-release arrangement. That makes the release rule a question for review, rather than assuming folding itself is slow.
A short review copy in your NOS workspace can help operations colleagues inspect the signal and the waiting interval together. If “Release” is ambiguous, clarify the static explanation to “Planner's instruction to begin the next operation.” Keep that wording change separate from the interval data and programmed calculations; a visual edit does not change the operating release rule.
For your real map, record who sends each instruction, what triggers it, and which operation receives it. Keep those information links distinguishable from the physical route, using labels as well as arrows.
Compare one future-flow assumption
Choose Proposed future model. It changes only W2 from 120 minutes to 30 minutes. Processing times and the other waits remain unchanged.
| Measure | Current teaching model | Proposed future scenario |
|---|---|---|
| Processing | 38 minutes | 38 minutes |
| Waiting | 60 + 120 + 42 = 222 minutes | 60 + 30 + 42 = 132 minutes |
| Elapsed within the boundary | 260 minutes | 170 minutes |
| Difference from current model | Reference | 90 minutes less, entirely from the W2 assumption. |
The ninety-minute difference is an arithmetic scenario result. It is not a measured improvement or proof that a different release arrangement can achieve it. Review the release process, constraints, and consequences before proposing how the shorter wait could actually occur.
Keep the current model available beside the future proposal. Replacing the original 120 with 30 everywhere would erase the comparison and make a desired condition look like an observation.
Leave an unmeasured interval unmeasured
Choose Missing interval case to see W2 without a supplied duration. The page retains that interval but withholds an exact elapsed total. It must not substitute zero, borrow the future scenario's thirty minutes, or present 260 as known for a different data state.
The example supplies no demand, available production time, inventory counts, uptime, or changeover measurements. It therefore supplies no takt-time calculation or conclusion about the right production-control method. Add relevant data from your actual stream before making those decisions.
When collecting your own times, define each start and end event, units, source, and observation conditions. Check that an apparent wait is not already inside another reported interval. One cleanly specified interval is more useful than a precise-looking total built from incompatible measurements.
Copy a prompt for the complete stream and comparison
Create one complete HTML value-stream review page.
Defined product family and start/end boundary: [PASTE]
Material operations and handoffs: [PASTE]
Order/planning/release information signals: [PASTE]
Process and wait intervals, units, sources, overlap rules: [PASTE]
Demand and other process data actually available: [PASTE]
Proposed future changes and their assumptions: [PASTE]
Map the whole material and information flow. Keep current evidence
separate from future hypotheses. Preserve missing data and interval
definitions. Do not equate processing with value-adding time or
invent demand, takt, inventory, uptime, changeover or observed savings.
Include this original fictional invitation-pack teaching model.
Boundary: order received to dispatch-ready; excludes shipping.
One pack, serial nonoverlapping intervals, all minutes:
W1 wait before printing 60; P1 print 12; W2 wait before folding 120;
P2 fold 8; W3 wait before packing 42; P3 pack 18.
Processing 12+8+18=38; waiting 60+120+42=222; elapsed 260.
Material: print→fold→pack. Information: order record→planner release
→production instructions. W2's modeled wait is associated with
the supplied batch-release arrangement; no real operation observed.
Show information vs material links with written labels.
Proposed future model changes only W2 from 120 to 30. Processing 38,
waiting 60+30+42=132, elapsed 170. Difference 90 is an assumption-based
scenario, not measured improvement or guarantee. All other intervals
stay unchanged. Keep original 120/current 260 visible for comparison.
Missing interval case makes W2 not supplied and withholds exact
elapsed total; do not use zero or borrow 30/120. Keep six interval
rows present. No demand, takt, inventory, uptime, changeover supplied.
Provide Current model, Proposed future model, Missing interval case
and Planner release selection. Show full flow, six-interval timeline,
counting basis and clearly labeled modeled totals. Planner selection
traces instruction to the receiving operation beside the W2 question.
Add a blank observation/source scaffold and temporary review notes;
preserve typing across views and confirm reset. No real batch release,
machine control, observed-outcome badge or automatic production advice.
At least 16px text, native labeled controls, visible focus, readable
flow/timeline records at 360px without overflow. Inline CSS/JavaScript,
no external assets, network or storage. Return complete HTML and the
actual observation questions needed to review the proposed change.
Check the generated current and future totals against the six rows. Then switch to the missing-data case and confirm that an exact elapsed total disappears. The flow should remain readable even when the calculation cannot be completed.
Take one whole-stream question to the observation
Before proposing a faster machine or a new release rule, watch the transition that W2 represents in your own process. Record when printing finishes, when folding can start, and what instruction or condition releases the work. Keep the actual waiting interval separate from any assumption about its cause.
Ask the operations team what would have to change for that interval to shorten, and what might happen elsewhere in the stream. Use those observations to revise the proposed flow; do not replace them with the example's thirty-minute target.