value-stream-mapping-examplesleanoperationsprocess-improvement

Value Stream Mapping Examples: 4 Real-World Maps · 2026

Compare four hypothetical value streams, separate processing from waiting and use explicit assumptions to interpret lead-time examples.

CodePic Team8 min read

Quick answer

Value-stream examples need a defined item family and consistent timing. Separate handling, waiting and overlap before calculating elapsed lead time.

How we verified this: Examples and numbers are hypothetical. Terminology is informed by Lean Enterprise Institute guidance; calendar and non-overlap assumptions are stated next to calculations.

The best value stream mapping examples are not pretty diagrams of an ideal process. They show a real item moving through a real system, including the waits that people normally explain away. That is why a map can reveal a striking result: a product may receive only minutes of hands-on work while taking days or weeks to reach a customer.

The four examples below use the same core question: where does the customer-facing item wait, why does it wait, and what evidence would show that the delay has actually improved? Open the value stream map template to adapt the manufacturing, software, or fulfillment scenes while you read.

Example 1: Manufacturing current-state map

Imagine a metal component moving through receiving, stamping, assembly, and shipping. A useful map shows the supplier and customer at the edges, production control above the process, and each physical operation in a horizontal line. Beneath every operation, place a data box: cycle time, changeover time, and uptime. Between operations, use inventory triangles with an observed quantity or days of stock.

The important comparison is not whether stamping is slower than assembly. It is the ratio between value-added time and total lead time. A map might show 45 seconds at receiving, 120 seconds at stamping, 200 seconds at assembly, and 30 seconds at shipping—less than seven minutes of processing—while inventory and scheduling waits produce twelve days of lead time.

That gap tells the team where not to start. Shaving ten seconds from assembly may matter less than reducing a five-day queue before it. The information flow often explains the queue: a weekly schedule, a batch release rule, or a forecast that does not match actual demand. Mark those instructions as dashed lines above the material flow so the map shows both the work and the reason it waits.

Example 2: Software delivery value stream

Software teams often map activity rather than flow: planning, coding, testing, and deployment all look busy. A value stream map instead follows one work item from idea to a customer-visible release. A simple current state may be idea → backlog → development → test → deploy → customer.

For a hypothetical feature, assume three days awaiting prioritization, five in backlog, two awaiting test capacity and one awaiting release: eleven days of waiting. If four further days are processing and all intervals use the same elapsed-day convention without overlap, total lead time is fifteen days, not sixteen. Define the calendar before comparing these values.

For this example, track work age, queue size, rework, deployment frequency, and the rule that moves a ticket to the next stage. A future state might introduce smaller batch sizes, a pull limit, or an explicit service-level expectation for review. The map is successful only if the team can compare the same measurements after the change.

Example 3: E-commerce fulfillment

In e-commerce, a value stream can start when a paid order is released and end when the customer receives it. The physical path is clear—pick, pack, ship, carrier delivery—but the waits are often hidden inside cut-off times, batch waves, labels, and carrier handoffs.

Map the order release signal above the flow, then record the time or queue between pick and pack, pack and handoff, and handoff and delivery. A common discovery is that picking takes minutes, packing takes minutes, and the largest variable is the order waiting for the next carrier collection. The improvement is not “make pickers work faster”; it may be moving the cutoff, changing wave design, or creating an exception route for high-priority orders.

Do not mix carrier transit time with internal handling without labeling it. The customer experiences the whole lead time, but the operation needs to distinguish what it controls from what it can only monitor and escalate.

Example 4: Service request flow

The item in a service value stream can be a maintenance request, insurance claim, patient referral, or grant application. Take a maintenance request: it arrives, is triaged, assigned, scheduled, completed, verified, and closed. The map should include the request signal, queue at triage, time awaiting customer access, vendor scheduling delay, repair time, and confirmation time.

The most valuable improvement may be a better intake form that routes emergencies immediately, not more reminders after a request is already stuck. Service maps work when they preserve human judgment: automate a receipt, task assignment, or reminder if useful, but keep safety, fairness, and exception decisions with a named owner.

How to read any example without copying it blindly

First, define one item family. Do not map every product, ticket, or customer type together. Next, walk the actual route and collect observations from the work, not from a procedure document. Third, separate processing time from waiting time. Finally, select one hypothesis to test, such as reducing batch size or making an approval rule explicit.

Avoid a future-state map that contains only improvements. Keep one measurable target beside each proposed change: queue size, wait days, first-pass yield, or lead time. Review it after a defined period and update the map with what actually happened.

Build your own example

Start with the scenario closest to your work in the value stream map template. Replace the process names with your own, add observed queue sizes and times, and draw the information signal that tells each step to begin. If the map does not make waiting visible, it is probably a process flowchart—not yet a value stream map.

Build a measurement ledger before drawing conclusions

For every example, record the item family, entry event, exit event, observation period and time convention. An order released at noon and delivered the next morning has an elapsed duration that is different from the operator’s working hours. Do not convert between them without an explicit calendar.

Keep processing, waiting and overlapping work distinct. If testing runs while another activity continues, adding both durations can double-count the same elapsed interval. The timeline should show whether activities are sequential or parallel before you sum them.

A useful ledger contains item identifier, stage, arrival, work start, work finish and departure. You can then separate queue waiting from active handling. Use hypothetical identifiers in a public diagram and preserve the actual evidence in the appropriate operational system.

Worked calculation: a hypothetical service request

Suppose a request waits two elapsed days before triage, receives one hour of triage, waits three elapsed days for an appointment and receives two hours of service. Assume the intervals are sequential and the example deliberately uses a continuous twenty-four-hour day.

Waiting totals five days, or 120 hours. Recorded handling totals three hours. Under those assumptions, total elapsed lead time is 123 hours. The handling share is three divided by 123, approximately 2.4 percent. Label it handling share rather than automatically calling every minute value-added.

The calculation is illustrative. It does not prove that the waits are avoidable or that speeding up triage is the best intervention. Appointment availability, customer access and necessary review can all influence the path. Collect reasons before selecting a change.

If the team instead measures business days, rebuild the intervals from the actual calendar. Do not reuse the 123-hour total while silently changing what a day means. Keep the old and new definitions visible if a reporting method changes.

Compare current and future states fairly

A future-state map is a hypothesis about a changed system. In the service example, the team might test whether earlier appointment confirmation reduces a particular wait. Assign an owner, the change to test, the affected request family and the measure used to judge it.

Preserve the same entry and exit events when comparing before and after. Check case mix, observation windows and unusual demand. A shorter average from a week of easier requests is not enough to establish that the change improved the process.

Include quality and rework. A faster handoff that creates more reopened cases may merely move the cost elsewhere. Record the definition of a completed request so a team cannot improve apparent lead time by closing unresolved work earlier.

Review the information flow as well as the physical or service steps. The queue might reflect missing approval, an absent schedule or batching, but waiting can also have other causes. The map should expose a question to investigate rather than declare every delay an information failure.

Keep the visual model separate from live operations

Use the map to connect the ledger, observed route and proposed changes. CodePic can display process boxes, queues and annotated timings, but it does not collect timestamps or calculate the improvement automatically. Maintain those measurements in a system that can support the required evidence.

Before sharing, ask a process owner to trace one real route against the draft. If exceptions have different stages, create a separate family or branch rather than averaging incompatible journeys into one reassuring picture.

Sources and verification

Official references used to verify the facts and comparisons in this article.

Frequently Asked Questions

What is a value stream mapping example?

A value stream mapping example is a completed current-state or future-state map showing how work, information, inventory, cycle time, and waiting move from a request to a customer outcome.

What numbers belong on a value stream map?

Record cycle time, changeover time where relevant, uptime, inventory or queue size, available time, and total lead time. Use actual observations rather than targets.

Can value stream mapping be used outside manufacturing?

Yes. In service and software work, the item moving through the value stream may be a request, case, order, feature, or application rather than a physical part.

Can I add working hours directly to elapsed days?

Only after defining and converting to a consistent calendar and avoiding overlapping intervals.

Is all processing time value-added time?

No. Classify the work explicitly; handling share alone does not establish customer value.

Related Posts