Value Stream Mapping: How to Draw a VSM, Step by Step

How to draw a value stream map in 8 steps: VSM symbols chart, a current-state map with real lead-time math, a future state, and a free template.

18 min read 12 sections Guide 4 of 14, Lean Foundations Updated

Value stream mapLead time is mostly waiting between the boxes

New to this topic?

Read these first to get the most out of this guide:

Value stream mapping (VSM) is a lean method for drawing every step that gets one product family from raw material to the customer, with the material flow, the information flow and a lead-time timeline on one page. You draw the current state from a walk of the floor, then a future state, then the plan between them. The eight steps:

  1. Pick one product family
  2. Set customer demand and takt time
  3. Walk the process from shipping back to receiving
  4. Fill in a data box for each process
  5. Count the inventory and convert it to days
  6. Draw the information flow
  7. Add the timeline and total it
  8. Design the future state and an action plan

Free value stream map template The steps in detail VSM symbols chart Worked example with numbers VSM software

What Is Value Stream Mapping?

Value stream mapping (VSM) is a lean method for drawing every step, value-adding or not, that it takes to get one product family from raw material to the customer, with both the material flow and the information flow on one page. The Lean Enterprise Institute defines it as diagramming "all the actions (value-creating and nonvalue-creating) needed to move a product or service from raw material to the arms of the customer." You draw the current state as it really runs today, then a future state that shows how it should flow, then a plan to get there.

Takt timeTakt = net available time ÷ customer demandThe Takt time guide

A value stream is the whole set of actions for one product family; a value stream map (the drawing itself) is different from an ordinary flowchart in three ways: it puts numbers on every step (cycle time, changeover, uptime, inventory), it shows how each step learns what to build next, and it ends in a timeline that adds up the total lead time against the minutes of actual work.

Why VSM Matters

Most managers know their individual process times. VSM shows what happens between processes (the waiting, the batching, the handoffs), which on most maps is most of the lead time. In the worked example below, a part spends 20 days in the building to get 154 seconds of work.

Mapping for the first time?

Start with one product family and one walk. The short floor guide Value Stream Mapping: Where to Start covers scope, what to record, and how to turn the map into actions with owners and dates.

Ready to model it?

VSM Pro is value stream mapping software that builds current and future state maps offline and does the takt, lead-time and WIP math for you, with what-if for the future state. Free 2-day trial.

How to Draw a Value Stream Map: 8 Steps

Steps 1 to 7 produce the current-state map, in the order you do them on the floor; step 8 turns it into a future state. Public guides from NIST MEP and AHRQ use the same sequence: choose the family, draw the process and material flow, add the information flow, collect the data, add the timeline, then design the future state.

USEREFILL
KanbanNothing is made until a card asks for itThe Kanban guide
Pick one product family

A family is a group of products that pass through similar steps and over common equipment in your downstream processes. Learning to See (Rother and Shook) is blunt about it: unless you have a small, one-product plant, drawing all your flows on one map is too complicated. Write down the family, how many part numbers are in it, and how much the customer wants, how often.

Set customer demand and takt time

Put the customer in the top right with daily demand. Work out takt time: available time per day divided by units per day. Every cycle time on the map gets compared against this number.

Walk the process from shipping back to receiving

Start at shipping and walk upstream to receiving. This follows the flow of customer value. Bring a pencil, stopwatch, and clipboard. Go to the gemba (actual workplace), don't map from a conference room.

Fill in a data box for each process

Draw one process box wherever the material flow stops. Under it, a data box: cycle time (how long one unit takes), changeover time, uptime %, batch size, number of operators, and available time per shift.

Count the inventory and convert it to days

Count WIP at every queue, buffer, and staging area. Convert it to time by dividing by daily demand: 900 parts in front of a step, with customers taking 450 a day, is 2 days of wait.

Draw the information flow

How does each step know what to work on next? Is it a schedule push, a kanban pull, or "whoever yells loudest"? Draw information flows across the top of the map: straight arrows for paper and verbal, zigzag arrows for electronic.

Add the timeline and total it

Draw a timeline at the bottom: wait time (days of inventory) on the upper level, processing time on the lower level. Total each row. The top row is your lead time, the bottom row your value-add time, and the ratio between them is what the map is for.

Design the future state and an action plan

Mark each problem with a kaizen burst, answer the future-state questions (takt, finished goods, flow, pull, pacemaker, levelling), draw the target map, and turn every burst into an action with an owner and a date. Without this step the map is a poster.

Simplified Value Stream (Before Improvement)
Receiving
CT: 2 min
Wait 4h
Assembly
CT: 8 min
Wait 6h
QC Check
CT: 3 min
Wait 2h
Shipping
CT: 5 min

Total lead time: 12h 18min → Value-add time: 18 min → Value-add ratio: 2.4%

VSM Symbols Chart

Value stream maps use a standard set of icons so anyone trained in lean can read anyone else's map. The set below follows the one popularized by Learning to See and taught in courses such as the University of Washington's IE 337. You need about a dozen of them for a typical first map.

ABC
HeijunkaLevel the mix and the volume, so every day looks like the averageThe Heijunka guide

Customer / Supplier

Factory outline. Supplier top left, customer top right, with demand written underneath.

Weld

Process box

One area where material flows. A new box starts wherever the flow stops and parts pile up.

C/T 45 sC/O 10 mUp 90%

Data box

Sits under a process: cycle time, changeover, uptime, operators, shifts, batch size.

I

Inventory

Triangle with an I. Write the count and the days it represents underneath.

Push arrow

Striped arrow. Material is made to a schedule and pushed on, whether the next step needs it or not.

Truck shipment

Deliveries in from suppliers and out to customers. Write the frequency: daily, 2x week.

Supermarket

A small, controlled stock the downstream process pulls from. Open side faces the supplying process.

Withdrawal (pull)

Curved arrow. The downstream process takes what it needs from a supermarket.

FIFOmax 225

FIFO lane

First in, first out with a cap on how many parts can sit in the lane. When it is full, upstream stops.

Kanban card

Production kanban tells a process to make; withdrawal kanban tells a material handler to move parts.

Signal kanban

Upside-down triangle. Used where a batch process makes a lot when stock falls to a trigger point.

OXOX

Load leveling

Heijunka box. Spreads the mix and volume evenly over the day instead of in big runs.

Manual information

Thin straight arrow: paper schedules, hot lists, phone calls, the supervisor's walk.

Electronic information

Zigzag arrow: ERP or MRP schedules, EDI orders, emailed forecasts.

Go see

Glasses. Someone adjusts the schedule by walking out and looking at what is on the floor.

Operator

Drawn in the process box with the head count next to it.

Kaizen burst

Starburst on the current-state map marking a problem the future state has to fix. Find its cause with root cause analysis (RCCA) before you pick the fix, and scope a burst big enough for an event with a kaizen charter template.

Timeline

Stepped line along the bottom. Upper steps are waiting (days), lower steps are processing (seconds).

VSM symbols table

The same symbols grouped the way most references group them: process, material, information and general. If you only learn five, learn the process box, data box, inventory triangle, push arrow and timeline.

GroupSymbolWhat it means on the map
ProcessCustomer / supplierOutside company or site; write demand or delivery frequency under it
ProcessProcess boxOne area where material flows continuously; a new box starts where the flow stops
ProcessData boxC/T, C/O, uptime, operators, shifts, batch size for the process above it
ProcessOperatorHead count working in the process
MaterialInventory triangleParts waiting; count them and convert to days of demand
MaterialPush arrowMaterial made to a schedule and sent on whether or not the next step needs it
MaterialTruck shipmentInbound or outbound delivery, with its frequency
MaterialSupermarketA small controlled stock that the downstream process pulls from
MaterialWithdrawal arrowThe downstream process takes parts from a supermarket (pull)
MaterialFIFO laneFirst in, first out queue with a maximum; full lane stops upstream
InformationManual information arrowPaper schedules, phone calls, hot lists
InformationElectronic information arrowERP or MRP schedules, EDI orders, emailed forecasts
InformationProduction / withdrawal kanbanCard that tells a process to make, or a handler to move, a fixed quantity
InformationSignal kanbanTriggers a batch when stock falls to a reorder point
InformationLoad leveling (heijunka) boxSpreads mix and volume evenly over the day
InformationGo seeSchedule adjusted by walking out to look
GeneralKaizen burstA problem the future state has to fix
GeneralTimelineWaiting days on the upper steps, processing time on the lower steps

Worked Example: A Current-State Map With Real Numbers

This is an illustrative example, not a client case. The numbers are made up but typical, and every one of them is shown with its math so you can check it and swap in your own. The product family is a line of painted steel brackets, made in four steps and shipped by truck every day.

WIP 6LEAD TIME
Little's lawWIP = throughput × lead timeThe Little's law guide
Customer demand450 brackets / day
Available time1 shift, 7.5 h = 27,000 s
Takt time27,000 ÷ 450 = 60 s
Current-state value stream map: supplier, stamping, welding, painting, assembly, shipping, customer, with inventory and a timeline totalling 20 days of lead time and 154 seconds of processing Steel Co. Coil, weekly Customer 450 / day Production Control MRP, weekly run Daily orders Weekly order Weekly schedule to each process Stamping Welding Painting Assembly Shipping C/T 4 sC/O 60 minUptime 85%1 operator C/T 45 sC/O 10 minUptime 90%1 operator C/T 50 sC/O 30 minUptime 80%1 operator C/T 55 sC/O noneUptime 100%2 operators IIIII 2,2505.0 days 2,7006.0 days 1,3503.0 days 9002.0 days 1,8004.0 days Truck in, Mondays Truck daily 5.0 d6.0 d3.0 d2.0 d4.0 d 4 s45 s50 s55 s Lead time 20 days Processing 154 s Burst on Painting: 50 s at 80% uptime = 62.5 s effective, slower than the 60 s takt. Days = pieces ÷ 450 per day. Illustrative example. Every process is pushed by its own weekly schedule from Production Control.

Swipe the map sideways to see all of it.

The lead-time math

Inventory on a map is converted into time by dividing it by daily customer demand. A Rolls-Royce supplier guide to completing a value stream map shows the same method: 174 pieces of in-process inventory against a requirement of 100 a day is 1.74 days. It is Little's Law (lead time = WIP ÷ throughput) applied one pile at a time.

Where the parts sitPieces countedMathDays of lead time
Raw coil (enough for)2,2502,250 ÷ 4505.0
Stamped, waiting for welding2,7002,700 ÷ 4506.0
Welded, waiting for paint1,3501,350 ÷ 4503.0
Painted, waiting for assembly900900 ÷ 4502.0
Finished goods, waiting for the truck1,8001,800 ÷ 4504.0
Production lead time9,0005 + 6 + 3 + 2 + 420.0 days

Processing (value-add) time = 4 + 45 + 50 + 55 = 154 s, about 2.6 minutes.

Value-add ratio = processing time ÷ lead time = 154 s ÷ (20 days × 27,000 s) = 154 ÷ 540,000 = 0.029%.

Takt check: effective cycle time = C/T ÷ uptime. Stamping 4 ÷ 0.85 = 4.7 s, welding 45 ÷ 0.90 = 50 s, painting 50 ÷ 0.80 = 62.5 s, assembly 55 ÷ 1.00 = 55 s. Painting is the only step slower than the 60 s takt, which is why the burst goes there.

Two things jump out. First, a bracket waits 20 days to receive under three minutes of work, and none of that waiting is anyone working slowly. Second, the map points at the constraint without anyone arguing about it: painting cannot keep up with takt on an 80% uptime, so the plant makes up the gap with overtime and stock. If the cycle times on your own map need checking, the Cycle Time Calculator and WIP and Little's Law Calculator do the same math, alongside the other free manufacturing calculators.

Do this math on your own floor

VSM Pro takes your demand, data boxes and inventory counts and builds this map, the timeline and the takt check for you, then lets you try the future state before you move anything.

See VSM Pro →

Reading a VSM: What to Look For

STOPPEDCHANGEOVER
SMEDMove internal work to external, then shrink what is leftThe SMED guide
Symptom on MapWhat It MeansAction
Large inventory triangles between stepsBatching or unbalanced processesReduce batch sizes, balance line
Information flows going to every step separatelyPush scheduling: no flowImplement pull signals (kanban)
One step with much longer CT than othersBottleneck constraining the systemApply Theory of Constraints
Effective C/T (C/T ÷ uptime) above taktThe step cannot keep up without overtime or stockRaise uptime, offload work, or add capacity
High changeover time at one stepLong setup blocking flowSMED (Single Minute Exchange of Die)
Low uptime % at a stepEquipment reliability issueTPM (Total Productive Maintenance)

Current State vs Future State Map

The current-state map is a diagnosis: what really happens today, drawn from the walk. The future-state map is the target design: how material and information should flow in, say, six to twelve months, using the same symbols. LEI describes it as "a target image of how the material and information should flow through the value stream." The improvement plan connects the two, one kaizen burst at a time.

MAKEUSE
Push and pullPush runs to a schedule; pull runs to a signal from downstreamThe Push and pull guide

The future state is built by answering a fixed set of design questions in order, the approach laid out in Learning to See:

  1. What is the takt time?
  2. Will you build to a finished-goods supermarket or straight to shipping?
  3. Where can you use continuous flow?
  4. Where do you need supermarket pull to control upstream production?
  5. At what single point (the pacemaker) will you schedule production?
  6. How will you level the production mix at the pacemaker?
  7. What increment of work will you release and take away at the pacemaker?
  8. What process improvements are needed to make all of this work?

Applied to the bracket example (still illustrative), the answers give this future state:

ItemCurrent stateFuture state
Raw coilWeekly truck, 5.0 daysTwice-weekly delivery, 2.0 days
Stamping to weldingPush, 2,700 pcs, 6.0 daysSupermarket with kanban, 450 pcs, 1.0 day. Stamping changeover cut from 60 to 20 min (SMED) so it can run smaller lots
Welding to paintingPush, 1,350 pcs, 3.0 daysFIFO lane, max 225 pcs, 0.5 day
Painting80% uptime, 62.5 s effective, above takt95% uptime through TPM: 50 ÷ 0.95 = 52.6 s, under takt
Painting to assemblyPush, 900 pcs, 2.0 daysFIFO lane, max 225 pcs, 0.5 day
Finished goods1,800 pcs, 4.0 daysFinished-goods supermarket, 675 pcs, 1.5 days
SchedulingWeekly MRP schedule to all four processesOne schedule point: welding is the pacemaker, pulled by kanban from finished goods and levelled in a heijunka box
Lead time20.0 days2 + 1 + 0.5 + 0.5 + 1.5 = 5.5 days
Processing time154 s154 s (unchanged)
Value-add ratio0.029%154 ÷ (5.5 × 27,000) = 0.10%

Lead time falls by (20 − 5.5) ÷ 20 = 72.5% without anyone working faster. That is the usual pattern: the future state changes the valleys of the timeline, not the peaks.

Before and After Example: Packaging Line

Current state: 14-day lead time from raw material to shipped product. Only 47 minutes of actual processing time. Value-add ratio: 0.23%.

Future state changes: Replaced batch scheduling with FIFO lanes, added supermarket pull between cutting and assembly, reduced changeover from 45min to 12min.

Result: Lead time dropped to 3.5 days. Same 47 minutes of processing, but 75% less waiting. On-time delivery went from 82% to 97%.

Value Stream Mapping vs Process Mapping

Both are flow diagrams, and teams often need both. The difference is altitude. A value stream map looks at a whole product family door to door and asks where the time goes; a process map (flowchart or swimlane) zooms into one process and shows every task, decision and handoff. Learning to See puts it as flow kaizen versus process kaizen: flow kaizen "focuses on material and information flow (which require a high vantage point to see) and process kaizen focuses on people and process flow."

STEP · KEY POINT · WHY
Standard workThe current best way, written down, so it can be improvedThe Standard work guide
 Value stream mapProcess map
ScopeOne product family, receiving to shipping, many processesOne process or procedure
Level of detailOne box per area where flow stopsEvery task, decision and handoff
ShowsMaterial flow, information flow, inventory, timelineSequence, decisions, who does what
NumbersC/T, C/O, uptime, WIP in days, lead time, taktOften none, sometimes step times
Main questionWhere does the lead time go, and how should it flow?How exactly is this step done, and where does it go wrong?
OutputFuture-state map and an improvement planA better procedure, standard work or SOP

A practical rule: map the value stream first to find the step that matters, then process-map that one step. If the team cannot yet agree where the stream starts and ends, a one-page SIPOC settles the boundaries before the walk.

High Level Value Stream Map

A high level value stream map shows the whole order-to-delivery stream with one box per department or site and the days each one adds. It comes before the detailed map: it tells you which part of the stream holds the lead time, so you know where the walk with a stopwatch is worth doing. Some teams call it an extended or door-to-door-plus map when it crosses company boundaries.

4 ERP3 MES2 CONTROL1 SENSE0 PROCESS
ISA-95 levelsFive levels stack from sensors at the bottom to the business system at the top; orders go down and results come up

Continuing the bracket example (still illustrative), the plant is one box among five:

Box on the high level mapLead timeWork time
Order entry (customer service)1.5 days20 min
Planning and MRP run3.0 days15 min
Plant: stamping to finished goods (the detailed map above)20.0 days154 s (2.6 min)
Regional warehouse6.0 days5 min
Truck to customer2.0 daysnone (transit)
Order to delivery32.5 daysabout 43 min

The plant holds 20 ÷ 32.5 = 62% of the lead time, so the detailed map belongs there first. The 4.5 days in order entry and planning are the next target, and they need an office map (touch time against queue time), not a shop floor one. The lean office guide covers that kind of stream.

Value Stream Mapping Examples by Setting

The method is the same everywhere; what changes is what sits in the queues and what counts as a process box.

NEXT STEP
Batch sizeBig batches pile in front of each step; cutting them shortens the waitThe Batch size guide
SettingProcess boxesWhat the inventory isTypical finding
Fabrication and assemblyStamping, welding, paint, assemblyParts between machinesBatch sizes set by long changeovers (SMED)
Office and order-to-cashOrder entry, credit check, scheduling, invoicingOrders, emails, files in queuesMinutes of touch time against days in inboxes (lean office)
WarehouseReceiving, putaway, pick, pack, shipPallets on the dock, orders waiting for a waveDock-to-stock time and wave release batching (lean warehousing)
Aerospace and long-cycle buildsMachining, outside processing, sub-assembly, final assemblyKits and parts waiting at outside vendorsOutside processing loops dominate lead time (aerospace VSM)

Value Stream Mapping Software and Templates

Draw the first map by hand. Once the map is drawn, a tool earns its place by doing the arithmetic (days of inventory, lead time, value-add ratio, the takt check) and by letting you test a future state before you move a machine. The options, from simplest:

A3The whole problem, story left to right, on one sheetThe A3 guide
OptionGood forDoes the lead-time math?Limits
Pencil and A3 paperThe first map, drawn during the walkNo, by handHard to share and to redo
Excel or Google SheetsThe data: one row per process, formulas for days and lead timeYes, if you build the formulasPoor for drawing the map itself
Diagram tools (Visio, Lucidchart, Miro)A clean drawing with standard VSM shapesGenerally no: the numbers are typed textChange a number and the totals do not follow
Dedicated VSM software (for example eVSM, VSM Pro)Maps where the numbers drive the timeline, plus what-ifYesAnother tool to learn

The free value stream map template takes your process and data boxes in the browser and works out lead time and the value-add ratio. VSM Pro is the offline value stream mapping software from SymplProcess: current and future state, takt and lead-time math, what-if, and maps saved as files on your own machine ($99, one-time, single user, with a free 2-day trial). For a class, the VSM Class Workbook walks a stream stage by stage. To check one pile at a time, the WIP and Little's Law calculator does the same math as the timeline.

Build Your Own VSM

Try mapping a simple value stream. Edit the process times and wait times to see how they affect total lead time and Process Cycle Efficiency.

CAPACITY
Capacity planWeekly load bars rise against the capacity line; the overloaded week shows in tapeThe Capacity plan guide

Mini Value Stream Map

Edit process times and wait times for each step. Watch how wait time dominates lead time — and how Process Cycle Efficiency (PCE) reveals the truth about your value stream.

Receive
→
Machine
→
Inspect
→
Ship
Lead Time Breakdown
120m
15m
60m
45m
30m
Value-AddWait / Non-Value-Add
286 min
Total Lead Time
31 min
Process Time
255 min
Wait Time
10.8%
PCE
Process Cycle Efficiency: Only 10.8% of total lead time adds value. Good progress — keep reducing wait times to reach world-class (25%+).

Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.

PlanTake the advanced knowledge check

Take the workbook to the floor

The Value Stream Mapping Workbook is a single self-contained file: build the stream stage by stage, put your own times and piles in, and it works out the metrics, the biggest opportunities, area capacity against a target, shared-resource load and a modelled future state as you go. It exports your data as CSV and a summary you can paste into a report. Works offline, on a laptop in a meeting room, with nothing to install.

Value Stream Mapping FAQ

CYCLETAKTLEAD
Takt, cycle and lead timeCycle time at or under takt; lead time is the whole waitThe Takt, cycle and lead time guide

What is value stream mapping?

Value stream mapping (VSM) is a lean method for drawing every step needed to get one product family from raw material to the customer, with the material flow, the information flow and a timeline on one page. Teams draw the current state as it runs today, then a future state showing how it should flow, then a plan to get there.

What are the steps of value stream mapping?

There are eight: (1) pick one product family, (2) set customer demand and takt time, (3) walk the process from shipping back to receiving, (4) record a data box for each process (cycle time, changeover, uptime, operators), (5) count the inventory between steps and convert it to days, (6) draw the information flow, (7) add the timeline and total it, (8) design the future state and an action plan.

How do you calculate lead time on a value stream map?

Convert each inventory pile to days by dividing the pieces by daily customer demand, then add the days. For example, 900 parts in front of a step with demand of 450 a day is 2 days. Add every pile on the map for the production lead time, and add the cycle times for the processing time. Processing time divided by lead time is the value-add ratio.

What is the difference between a value stream map and a process map?

A value stream map covers a whole product family door to door at a high level, with inventory, information flow and a lead-time timeline. A process map zooms into one process and shows every task, decision and handoff. Map the value stream first to find the step that matters, then process-map that step.

What is the difference between a current state and a future state map?

The current-state map shows how material and information flow today, drawn from what you saw on the floor. The future-state map is the target design, usually six to twelve months out, built by answering questions about takt, continuous flow, supermarkets, the pacemaker and levelling. The improvement plan is the list of changes that gets you from one to the other.

What symbols are used in value stream mapping?

The common ones are the customer and supplier factory icon, process box, data box, inventory triangle, push arrow, truck shipment, supermarket, withdrawal arrow, FIFO lane, kanban cards, load-levelling box, manual and electronic information arrows, go-see glasses, operator, kaizen burst and the timeline. About a dozen cover most first maps.

How long does value stream mapping take?

For one product family, a walk and a draft current state can be done in a day. Learning to See suggests that in about two days a team should have a future-state map drawn to the point where implementation can begin. Do not wait for perfect data; note what you estimated and check it on the next walk.

What is a high level value stream map?

A high level value stream map shows the whole order-to-delivery stream with one box per department or site (order entry, planning, production, warehouse, delivery) and the days each one adds. It is used to choose which stream to map in detail and to show where the lead time sits before anyone draws process boxes and data boxes.

Can I make a value stream map in Excel?

Yes. Excel works for the data: one row per process with cycle time, changeover, uptime and inventory, and formulas for days of inventory, lead time and value-add ratio. It is clumsy for the drawing itself, so most teams sketch the map on paper and keep the numbers in a sheet, or use a tool that does both.

Do you need software for value stream mapping?

No. The first map should be drawn in pencil on the walk, so the team sees the floor rather than a screen. Software helps afterwards, when you want the takt, lead-time and WIP math done for you, a clean copy to share, and a way to test the future state before changing the floor. VSM Pro from SymplProcess does this offline.

Sources

The bracket and packaging-line examples on this page are illustrative, not client data.

Take this to a room

The running order

For a team about to map a value stream. They should leave knowing to walk it backwards from shipping, to convert every pile into hours, and to expect the timeline to be mostly waiting.

7 beats · 9 min
  1. 1

    What a map is for

    Everyone already knows their own process times. A value stream map is about what happens between processes.

    • The waiting, the batching, the handoffs.
    • On most maps that gap is most of the lead time.
    • Nobody owns the space between two departments, which is exactly why it hides.

    Ask the room Who owns the queue between our two busiest steps?

  2. 2

    Walk it backwards, on foot

    Start at shipping and walk upstream. That follows the flow of customer value, and it stops you mapping what you assume.

    • Pencil, stopwatch, clipboard. Not a conference room.
    • Backwards keeps you honest about what the customer actually receives.
    • If you did not walk it, you did not map it.
  3. 3

    What to write at each step

    Six numbers per station, and none of them is an opinion.

    • Cycle time, changeover time, uptime per cent.
    • Batch size, operators, available time per shift.
    • If a number is disputed on the floor, that is a finding in itself.
  4. 4

    Turn every pile into hours

    WIP counts mean nothing to an audience. Time does.

    • Count WIP at every queue, buffer and staging area.
    • 500 units in front of a step that handles 100 an hour is 5 hours of wait.
    • Now the pile is on the same axis as the process time.

    Ask the room What is the biggest pile on our floor, in hours?

  5. 5

    Draw the information flow too

    Half the map is the question: how does each step know what to work on next?

    • A schedule push, a kanban pull, or whoever shouts loudest.
    • Information flows go across the top, material along the bottom.
    • Where the information is unclear, the material is usually late.
  6. 6

    The timeline is the punchline

    Cycle time on the rises, wait time in the valleys. Total them and the ratio does the arguing for you.

    • An example: 14-day lead time, 47 minutes of processing. Value-add ratio 0.23 per cent.
    • Nothing about that number is unusual.
    • It is not a criticism of anyone's work rate.
  7. 7

    Then the future state

    The current map is a diagnosis. The changes come from the valleys, not the rises.

    • In that example: FIFO lanes instead of batch scheduling, a supermarket between cutting and assembly, changeover 45 down to 12 minutes.
    • Result: 3.5-day lead time. Same 47 minutes of processing, 75 per cent less waiting.
    • On-time delivery 82 to 97 per cent.

    Ask the room Which stream do we map, and who walks it with us?