PublishedISO 9001:2026 published 16 Sept 2026 · 2015 certificates must transition by 30 Sept 2029What changed →
Internal Auditor course (ISO 19011:2026):free until 31 Oct · then $59 for three monthsStart free now →
← All value stream map examples

Clothing & textiles · worked example

Value stream map example: workwear shirts

A monthly fabric delivery, cutting in big lays, and bundles of 300 moving through a 30-operator sewing line that is just over takt once re-sews are counted. Fabric and finished cartons hold more than half of the lead time. The guide's future state: supermarkets after cutting and sewing, buttons, pressing and packing joined into one cell that sets the pace, and fabric twice a week instead of monthly.

The current state

Workwear shirts (8 sizes, 3 colours): 30 000 shirts a month (customer: Uniform distributor), on 1 shift of 9 hours. That makes 1 500 shirts a day and a takt time of 19.8 seconds. Sewing line is over takt once stoppages and rework are counted (Sewing line: 20.8 s effective against 19.8 s).

Lead time
29 days
raw material to customer
Processing time
587 s
actually worked on
Flow efficiency
0.068%
processing ÷ lead time
Schedule points
5
places told what to make
CURRENT STATEExample — workwear shirtsSeason forecastMonthly orders3-month forecastMonthly orderWeekly scheduleWeekly scheduleWeekly scheduleWeekly scheduleDaily dispatch listTextile millFabric rollsMonthlyUniformdistributor30 000 shirts/month1 500 shirts/dayTakt 20 sPack 20 shirts1 shiftProduction controlERPMonthlyTwice weeklyI22 500 shirtsFabric rolls22 500 shirts = 15 days of customer demandI6 000 shirtsCut bundles6 000 shirts = 4 days of customer demandI4 500 shirtsSewn4 500 shirts = 3 days of customer demandI3 000 shirtsButtoned3 000 shirts = 2 days of customer demandI1 500 shirtsPressed1 500 shirts = 1 day of customer demandI6 000 shirtsFinished cartons6 000 shirts = 4 days of customer demandFabric cutting2SharedLoad21% of taktEffective C/T 4.2 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T4 sC/O30 minUptime95%FPY99.5%Batch1 200 shirtsSewing line30Load105% of taktEffective C/T 21 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T18 sC/O20 minUptime92%FPY94%Batch300 shirtsButtons & buttonholes2Load68% of taktEffective C/T 13 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T12 sC/O10 minUptime90%FPY99%Batch300 shirtsPressing & finishing3Load81% of taktEffective C/T 16 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T15 sC/O0Uptime95%FPY98%Batch300 shirtsInspect & pack3Load83% of taktEffective C/T 16 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T16 sC/O0Uptime98%FPY99.5%Batch—15 days4 s4 days540 s3 days12 s2 days15 s1 day16 s4 daysWAITING (STOCK)PROCESSING (VALUE-ADDED)Lead time29 daysProcessing587 sFlow eff.0.068%Q6% re-sew
Current-state map. Every company, name and number in this example is invented.

What the improvement guide recommends

Run through the builder's nine future-state questions, accepting each recommendation, this value stream gets one pacemaker (Buttons & buttonholes + Pressing & finishing + Inspect & pack) and these 11 actions — each one a kaizen burst on the future-state map:

  1. 1SMEDCut Fabric cutting changeover from 30 to 15 min (SMED)
  2. 2Pull (kanban)Set up a kanban supermarket after Fabric cutting (about 2 250 shirts); Fabric cutting makes only what Sewing line withdraws
  3. 3SMEDCut Sewing line changeover from 20 to 1 min (SMED)
  4. 4Quality at sourceRaise Sewing line first-pass yield from 94% to 99% (root cause, error-proofing)
  5. 5Pull (kanban)Set up a kanban supermarket after Sewing line (about 2 250 shirts); Sewing line makes only what Buttons & buttonholes + Pressing & finishing + Inspect & pack withdraws
  6. 6Continuous flowBuild a continuous-flow cell: Buttons & buttonholes + Pressing & finishing + Inspect & pack (8 operators, one piece at a time)
  7. 7SMEDCut Buttons & buttonholes changeover from 10 to 5 min (SMED)
  8. 8PacemakerSend the customer schedule to Buttons & buttonholes + Pressing & finishing + Inspect & pack only — every other process is triggered by kanban or FIFO
  9. 9HeijunkaLevel the mix and volume at Buttons & buttonholes + Pressing & finishing + Inspect & pack: release one pitch of work (20 shirts) at a time from a load-leveling box
  10. 10Pull (kanban)Hold finished goods in a supermarket of about 2 250 shirts (1.5 days) that shipping withdraws from
  11. 11Supplier pullAgree twice weekly deliveries with Textile mill and refill a raw-material supermarket from kanban

The future state: 29 days down to 7.5 days

Lead time
7.5 days
from 29 days (−74%)
Stock
11 250 shirts
from 43 500 (−74%)
Working capital freed
R5.16 million
at R160 a unit
Schedule points
1
from 5
FUTURE STATEExample — workwear shirtsSeason forecastMonthly orders3-month forecastKanban call-offOXOXPitch 6.6 minTextile millFabric rollsTwice weeklyUniformdistributor30 000 shirts/month1 500 shirts/dayTakt 20 sPack 20 shirts1 shiftProduction controlERPTwice weeklyTwice weekly4 500 shirtsFabric rolls4 500 shirts = 3 days of customer demand2 250 shirtsCut bundles2 250 shirts = 1.5 days of customer demand2 250 shirtsSewn2 250 shirts = 1.5 days of customer demand2 250 shirtsFinished cartons2 250 shirts = 1.5 days of customer demandFabric cutting2SharedLoad21% of taktEffective C/T 4.2 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T4 sC/O15 minUptime95%FPY99.5%Batch1 200 shirtsSewing line30Load100% of taktEffective C/T 20 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T18 sC/O1 minUptime92%FPY99%Batch300 shirtsPACEMAKERButtons & buttonholes…8CellLoad100% of taktEffective C/T 20 s (C/T ÷ uptime ÷ yield) against takt 20 sC/T16 sC/O5 minUptime83.8%FPY96.5%Work117 s3 days4 s1.5 days540 s1.5 days43 s1.5 daysWAITING (STOCK)PROCESSING (VALUE-ADDED)Lead time7.5 daysProcessing587 sFlow eff.0.26%SMED 30→15 minSMED 20→1 minYield 94→99%Flow cellSMED 10→5 minLevel the mixTwice weekly deliveries
Future-state map drawn by the builder's guide: supermarkets and kanban loops, FIFO lanes, one pacemaker fed from a load-leveling box, and kaizen bursts where a process has to improve.
Open it and change the numbers →Free, no sign-up. The map is saved in your own browser.

More value stream map examples

New to the symbols? See the VSM symbols cheat sheet.

Get the free Value Stream Walk Kit (Excel)

Free, instant download. We'll only email you the occasional practical quality update — no spam, unsubscribe anytime.

Turning the map into results

Mapping a value stream and not sure what to fix first?

Stuck between a current-state map and a future state that actually happens on the floor — too much stock, a bottleneck nobody owns, a kanban loop that never stuck? Tell us what you're seeing. We'll look at it and suggest a practical next step, or connect you with people we trust who can help.

Email hello@qlause.app

No sales pitch, no obligation — we read every message.