■ Lean Fundamentals · A Visual Explainer ■
One Piece
at a Time
Two identical production lines get the same job: ten pieces, three steps. One works in batches. The other moves one piece at a time. The difference is bigger than it looks.
Scroll
Walk through almost any factory — or office — and you will find work moving in piles. Cut a hundred parts, then fold a hundred parts. Approve a stack of invoices, then enter a stack of invoices. Batching feels efficient: you set up once and crank.
Lean practitioners call the alternative one-piece flow: finish a piece completely and pass it on before starting the next. To see why it wins, we built two lines and gave them a race. Scroll to run it.
The Experiment
The scoreboard
Both lines did exactly 30 minutes of hands-on work. Only the movement changed.
| Result | Batch | Flow |
|---|---|---|
| First piece in the customer's hands | 21min | 3min7× sooner |
| Entire job complete | 30min | 12min60% less time |
| Half-finished pieces sitting in piles (peak) | 9 | 0no piles at all |
When Something Goes Wrong
Speed is only half the story. Now run the race again — but this time the fold station is set up wrong, and every fold it makes is defective. Nobody on either line knows yet. You, however, get to watch.
Batch line
By the time the first bad piece reaches packing, all ten have already been folded wrong. The entire batch is scrap or rework — and the evidence of what went wrong is 11 minutes cold.
Flow line
The very first piece exposes the problem at minute 3, while the trail is fresh. One piece is affected; the station is fixed before piece two is folded, and the job still finishes by minute 14. Flow doesn't just move faster — it learns faster.
The Footprint
Piles don't just cost time — they cost square feet. Every buffer in the batch run needs racks to hold it, pallets to move it, and aisles wide enough for the forklift that feeds it. Shrink the batch, and the piles disappear; the stations can pull within arm's reach of each other — the compact cell layout lean factories are known for.
Less floor space, less handling, less to track — and a layout where a problem at one step is an arm's length from the next.
Why It Matters
Nothing about the work itself changed in this race — not the people, the machines, or the minutes of effort. What changed was the batch size, and with it four things every operation cares about.
Lead time collapses. Customers feel minute 3, not minute 21. In a real value stream, batching is why a product with 30 minutes of actual work can take six weeks to deliver.
Cash stops hiding in piles. Every half-finished piece in a buffer is money you've spent but can't sell yet. Flow keeps work-in-process — and the floor space, handling, and tracking it demands — near zero.
Problems surface immediately. A batch buries a defect under nine identical copies. Flow puts it in your hands within minutes, while the cause can still be found and fixed.
Space comes back. The buffers and aisles a batch needs are pure overhead. Pull the piles out and the work folds into a compact cell, freeing floor you can use for the next product instead of the last one's leftovers.
None of this means batching is always irrational. Long changeovers, ovens that cure 50 parts at once, shipments priced by the pallet — these push real operations toward batches. The lean response isn't to accept that, but to attack the reason: shrink changeover times, right-size the equipment, and keep driving batch sizes down toward one.
And the lesson travels well beyond the factory. Emails answered in a Friday pile, invoices approved monthly, software released quarterly — all batches, all with the same hidden cost. Wherever work waits in a stack, minute 21 is hiding inside it.
Frequently asked
- What is one-piece flow?
- Moving one piece completely through each step before starting the next, instead of processing a whole batch at one step before the batch moves on.
- Why is one-piece flow faster if the work is the same?
- The hands-on time is identical; flow just overlaps the steps (all stations work at once) and stops parking finished work in buffers, so the first piece — and the whole job — finishes far sooner.
- Doesn’t batching save on setups and changeovers?
- It can, which is why long changeovers, shared ovens, and pallet-priced shipping push toward batches. The lean answer is to attack the cause (SMED/quick changeover, right-sized equipment) and drive batch size toward one, not to accept large batches.
- How does flow improve quality?
- A defect in a batch hides under every later copy and isn't caught until inspection; in flow the very next step catches it within minutes, while the cause can still be found and fixed.
Related
Founder of Kaizumi, an AI-powered Lean training platform. More about Matthew →
Updated June 9, 2026 · Drafted with AI assistance and reviewed by Matthew Savas for accuracy.