Skip to content

Measure · Free tool guide

Value Stream Mapping: guide & examples

Value Stream Mapping shows material or service flow and information flow across a process, with timing, demand and inventory information where applicable.

5 practical steps · 2 worked examples · Editable practice worksheet

Reading is free. Tool access requires a verified account; no manual beta approval or payment is required.

What is it, and why use it?

Value Stream Mapping shows material or service flow and information flow across a process, with timing, demand and inventory information where applicable.

It helps teams examine the whole flow rather than optimizing one activity while queues remain elsewhere.

Explore the Value Stream Mapping features and local-file workflow

When to use it

Use it when handoffs, waiting and end-to-end performance matter across several steps or departments.

When another tool fits better

Use a Flowchart for detailed routing or Time Study for direct activity observations. A VSM needs more than a list of unconnected boxes to support flow calculations.

Before you start

  • A defined service or product family and observation period.
  • Measured per-unit times, demand and available time with compatible units.
  • The actual connected material/service route and information exchanges.

Use fictional or approved non-sensitive information. Do not include patient details or proprietary records in practice worksheets.

Step-by-step in CI Tools

  1. Add the appropriate editable process, inventory and information symbols. Connect material/service and information flows according to observed work.

  2. Record per-unit times in minutes and available time for the named operating period. Label estimates and unknown values.

  3. For branching maps, select an ordered material-connected path before interpreting path-specific metrics.

  4. Review completeness and compatibility of inputs before using lead time or process cycle efficiency (PCE). Unknown value-added time is not zero.

  5. Create an independent future-state copy to compare with the captured baseline, test the proposed changes and save both maps locally.

Use complete, compatible inputs for flow metrics

Lead time and PCE depend on the selected connected route. Takt requires demand and available time for the same period. Separate estimates from observations and review branches, parallel activity and inventory assumptions before comparing maps.

Completed worked examples

Demonstrations only: all organizations, observations, targets and results below are fictional. They are not clinical instructions or universal performance standards.

Healthcare operations — fictional

Referral flow overview

Starting information: A fictional service maps intake, review and scheduling on a single observed path.

Completed demonstration: Referral flow overview
Processing / waiting12 minutes processing and 108 minutes waiting, all sequential
Lead time120 minutes
PCE exampleIf only 6 minutes are agreed value-added: 6/120 × 100 = 5%

What the result means: The value-added classification must be agreed, not inferred from “busy” time. The calculation applies only to this complete path and period.

General business — fictional

Sample order flow

Starting information: A fictional operation maps a product family during one operating day.

Completed demonstration: Sample order flow
Demand / available time60 units per day / 420 available minutes per day
Takt example420/60 = 7 minutes per required unit
ReviewA measured 9-minute station cycle warrants capacity investigation

What the result means: Takt describes the demand pace, not an instruction to work faster. Review variability, parallel resources and capacity assumptions before changing the method.

Practise in a separate worksheet

Open the tool’s built-in synthetic sample as a new editable worksheet. It may differ from the worked demonstrations above. It never replaces an existing worksheet. Save any work you want to retain to your computer.

Open built-in practice worksheet

You’ll be asked to log in if needed. No worksheet is created just by reading this page.

Common mistakes and how to avoid them

  • Mixing per-day demand with per-week available time: align operating periods.
  • Treating unknown value-added time as zero: complete the observation.
  • Calling the highest cycle time a proven bottleneck: check capacity and the connected flow.

Interpret the result

Interpret the selected path and the assumptions behind each metric. A low PCE suggests substantial non-value-added elapsed time but does not identify its cause. Review current and future states with observed results, not just different layouts.

Record the assumptions and unanswered questions alongside the result. Use the relevant local review process before making operational decisions.

Credible further learning

These independent educational resources explain the methods. They do not endorse CI Tools Suite. Some external resources have their own access requirements.

Resource links reviewed 29 October 2026. Our interface instructions and fictional examples are original CI Tools learning material.

Put the method into practice

Start a new worksheet, use the guide beside your work and keep an editable .citools copy on your computer.

Try This ToolChoose another tool

Back to guide contents ↑