Worksheet

Value Stream Mapping Worksheet

Interactive worksheet to map an end-to-end value stream, collect measured times and counts, reveal handoffs and waits, quantify WIP and defects, check map quality, and plan prioritized experiments with owners and follow-up.

Interactive Tool

Value Stream Mapping Worksheet

Quick intro

This interactive worksheet helps you map a target process end-to-end, collect evidence-backed times and counts, reveal handoffs and waits, and turn findings into prioritized experiments. Use observed measurements where possible (time samples, WIP counts, defect rates). If you have more than twelve steps, copy this worksheet or track additional steps in your notes.

Practical tips: walk the process with the team, time several sample items at each step, count WIP at handoffs, and record who owns each step. Define and record your measurement units, sample size, and evidence source up front. Avoid mapping opinions alone — record measurements and the evidence source. Use the Map Quality checklist below to avoid superficial diagrams.

Why this matters: a good value stream map is a discovery-to-experiment workflow: map with evidence, form hypotheses, design a measurable experiment, assign an owner, and schedule follow-up checks.

Name the full process you are mapping (example: 'Customer Order to Ship').
Clear start point for the mapping (example: 'Order received').
Clear end point for the mapping (example: 'Product delivered to customer').
Who receives the output of this process and what they value.
Person accountable for this overall process. Naming an owner makes follow-through more likely.
Date this mapping was performed (YYYY-MM-DD).
Choose the unit you will use consistently across this worksheet (all times should use the same unit).
Practical suggestion: time at least 8–15 items per step where possible. Enter the sample size you will use.
Who will collect measurements, sample size, frequency, and tools (stopwatch, system logs, counts). Example: 'Time 10 consecutive items at each step during morning shift; count WIP at 10:30 daily for 3 days.' This field captures your measurement protocol — completing it reduces bias and strengthens experiments.
Where the numbers came from (observation, system timestamp, historical log, interviews). Specify samples and any filters (e.g., 'orders > $50 only').
Enter how many steps you will fill below (1-12). Use up to twelve rows in this worksheet.
For tools that don't render repeated rows, paste step details here as CSV rows: Step name | Process time | Wait time | WIP | Defects per 100 | Notes. Otherwise use the individual step fields below.
Short name for step 1 (e.g., 'Receive order').
Active processing time for a single unit — use the unit selected above.
Typical waiting time between this step and next.
Typical work-in-progress (number of units) at this step or queue.
Defects or rework observed per 100 units (or % as number), if measured.
Describe handoffs, special resources, constraints, tools, or frequent issues at this step.
Name for step 2.
Active processing time for a single unit.
Measured end-to-end lead time from scope start to scope end, if observed.
If your renderer supports calculation this can be auto-filled. Otherwise compute offline as the sum of step process times and paste here.
A simple indicator of flow efficiency. Compute as (total process time / total observed lead time) * 100. Enter as a percent number.
Check all wastes you observed in this value stream.
Which step appears to limit throughput? Enter the step name from above.
List 2–5 hypotheses causing the constraint or wastes.
Select interventions that could address the constraint. Use these suggestions as starters — adapt to your context.
A short name for the first experiment you will run to address the bottleneck.
If we [change], then [effect] measured by [metric]. Example: 'If we reduce batch size from 50 to 10, then lead time will drop by 30% measured by average order-to-ship minutes.'
Metric name and how it will be measured (e.g., 'Order lead time (minutes) — measured from system timestamp A to B').
Current measured value for the chosen metric.
What you aim to achieve during the experiment.
How many days the experiment will run before assessing results. If you name an experiment, name an owner and duration so results are actionable.
Who will run the experiment and collect the measures. Assigning an owner increases follow-through.
People, materials, tooling, approvals, or data needed to run the experiment.
Potential negative impacts and how you'll limit them.
Rate how urgent this improvement is for the organization.
1.0 10.0
Rate the expected business impact if successful.
1.0 10.0
After scoring, summarize priority and list 3 immediate next steps with owners and dates (format owner: action — due date).
Quick checks to prevent superficial mapping. Confirm these before you finalize the map.
Do you plan a follow-up mapping or audit to verify results?
When you will re-check (date or event).
Anything else the team should know or record during this mapping.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.