One-piece flow: how single-unit flow cuts waiting and WIP

Four traits define it:

Continuous flow is a close relative. Lean writers sometimes use it more broadly to include small, steady batches with little delay. Strict one-piece flow moves single units; real lines often mix single transfers with controlled buffers or a batch step that cannot be avoided. The useful question is whether work moves steadily or spends time waiting.

Three stations assemble, test and package a product. Each step takes 1 minute per unit. The order is 10 units, each station has its own operator, and setup, travel and defects are ignored:

The work content is identical. What changes is when downstream work can start: with single transfers the three stations overlap. In general, with n units and k equal steps of t minutes, batches finish after n × k × t and single-unit flow after (n + k − 1) × t. Real lines add setups, travel and variation, so treat this as the shape of the effect, not a forecast.

Each benefit has a mechanism and a way to confirm it:

Do not book every removed rack as a saving. Freed space and time are only cash savings when a real cost goes away; otherwise record what the space and time are now used for.

These are two separate decisions:

Moving single units does not mean changing products after every unit. A cell can run the same model all morning and still pass each unit on alone. Write both numbers down at each step; often the first test is changing the transfer rule while the production schedule stays the same.

The patterns at a glance:

Not every batch process is badly run. Compare the real route, transfer sizes, setup needs and demand, and look at the full result rather than the measure that flatters one option.

Illustrative candidates. For each, ask whether the next step can take a single item and what stops it today:

The last case is common. Some processes, such as ovens, plating or painting, run in batches for good reasons. Improve flow where you can and manage the remaining joints on purpose. To pick a candidate, follow one real item through its whole route and note where it stops, who decides when it moves and what information travels with it.

Removing inventory removes the cushion that hid these problems, so put them in place first:

When two steps cannot sit side by side, a FIFO lane keeps the sequence. The first item in is the first out, and a full lane tells the supplying step to stop. For each lane, write down:

A lane is a visible design choice the team can challenge, not permission to store material wherever space is free.

Start with a bounded pilot before rearranging a whole plant:

1. 1

   Choose a product family. List the products included, where the pilot starts and ends and the customer need it must meet. Note products left out because their routes differ.

2. 2

   Walk the current route. Follow sample units through processing, waiting, moving, inspection and rework, and write down the real handoff rules, including informal ones. A value stream map is a good format.

3. 3

   Set a baseline. Agree measure boundaries and record lead time, WIP, good output, quality losses and stops, across shifts and variants.

4. 4

   Design the connection. Describe the work sequence, transfer rule, refill signal and any FIFO lanes. Review layout, handling and equipment with the people who do the work.

5. 5

   Prepare the response to problems. Name who supports the cell, how help is called and how suspect material is held, before removing the inventory that used to separate the steps.

6. 6

   Trial and review. Run under controlled conditions, compare with the baseline, record what failed as well as what improved and revise before expanding.

Set the decision rule before the pilot starts, for example: shorter lead time with no drop in good output, quality or operator workload. Otherwise an attractive layout becomes the only proof of success.

Use a small, balanced set of measures and read them together:

flow efficiency = value-adding time ÷ total lead time

Set the process boundary first. A required inspection may be needed work even though it does not change the product. The flow efficiency calculator does the arithmetic.

1. 1

   Flow means never stopping. Stopping to protect quality is part of the design. Passing on bad work is not flow.

2. 2

   Low inventory means no inventory. Standard work can include set in-process stock, and pull systems use controlled refill stock.

3. 3

   A compact cell proves flow. Check whether work really moves steadily and meets demand. Layout supports the method; it does not replace it.

4. 4

   Every step must flow one by one. Some batch steps stay. Manage the joint instead of forcing single units everywhere.

5. 5

   Flow is only for factories. The same idea applies to requests, claims and code changes that wait in batches.

Start with a bounded process and a measurable problem, and test whether the new method cuts waiting while keeping quality, output and workload steady.