Key takeaways
Short answer: One-piece flow and batch production are opposite ways to move work through a process. One-piece flow moves a single unit through each step and on to the next, one at a time, in a continuous stream. Batch production processes a whole lot at each step before moving the batch forward together. One-piece flow dramatically cuts lead time and work-in-process and surfaces problems instantly; batching is sometimes necessary but builds inventory and hides issues. The lean ideal leans toward flow. For the lot-sizing trigger, see push vs pull production.
One-piece flow — also called continuous flow or single-piece flow — moves one unit through the process at a time: a unit completes a step and immediately moves to the next, rather than waiting for a batch of companions. The whole process is balanced so units flow through it singly and steadily, like a smooth stream rather than a series of pools. The defining benefits are speed and visibility. Lead time collapses because no unit waits in a batch for the others; work-in-process drops to almost nothing; and a problem — a defect, a stoppage — is felt immediately downstream, because there is no buffer of batched units to hide it. One-piece flow is the lean ideal of flow, demanding balanced, reliable steps but rewarding them with short lead times and fast feedback.
Batch production processes a group of units together at each step before the whole lot moves on. A step works through its batch, then the batch waits and moves to the next step as a unit. Batching is sometimes a deliberate, sensible choice — when a step has a long changeover that you want to amortise over many units, when a process is inherently batch (a heat-treat oven, a plating bath), or when transport between distant steps favours moving lots. Its strength is in those specific economics. Its weaknesses are systemic: batches create work-in-process inventory, lengthen lead time (a unit waits for its whole batch at every step), and hide problems — a defect made early in a batch may not be discovered until the whole lot reaches inspection, by which time the error has been repeated many times.
The distinction is simply whether work moves singly or in groups. One-piece flow moves units one at a time; batch production moves them in lots. The consequences, though, are large and systemic. Lead time: in one-piece flow a unit only ever waits for one operation, while in batching it waits for its entire batch at every step, so lead time can be many times longer. Inventory: one-piece flow holds almost no work-in-process, batching holds a lot. Problem detection: one-piece flow surfaces a defect within one unit, batching can hide it across a whole lot. This is why lean strongly favours flow — not as dogma, but because moving single units, where feasible, attacks lead time, inventory, and hidden defects all at once.
Four steps, each taking one minute per unit, processing 100 units. Under batch production with a batch of 100: step one works for 100 minutes on all units, then the batch moves to step two for 100 minutes, and so on — the first finished unit emerges only after roughly 300-plus minutes, and a defect introduced at step one is not caught until the batch reaches a later check, by which point 100 flawed units exist. Under one-piece flow: the first unit passes through all four steps in about four minutes and is done, with subsequent units following one a minute behind — and if step one starts producing a defect, it is caught within a unit or two, not a hundred. Same work content, dramatically different lead time and dramatically different defect exposure.
One-piece flow is the ideal, but batching is not always wrong — it can be the right choice where the economics or the process genuinely demand it. A step with a long, expensive changeover may need to run a batch to amortise the setup (which is exactly why reducing changeover time via SMED matters — it shrinks the batch size that flow can economically support). Some processes are inherently batch — ovens, baths, curing — and cannot be made single-piece. And distant or shared resources sometimes favour moving lots. The lean approach is not to ban batching but to relentlessly shrink batch sizes toward one wherever feasible, attacking the changeover and layout constraints that force large batches, so the process moves as close to flow as the real constraints allow.
One-piece flow and OEE reinforce each other through fast feedback. Because flow surfaces a defect or a stoppage within a unit or two rather than across a whole batch, it makes quality and downtime losses immediately visible — exactly the visibility that drives OEE improvement, the same dynamic as pull production. Batching, by contrast, lets losses hide inside work-in-process: an unreliable machine is masked by the buffer of batched units, so its true OEE cost stays invisible. There is a dependency too — one-piece flow only works on reliable, balanced equipment, so good OEE (high availability) is a prerequisite for sustaining flow. Improving OEE and moving toward flow go hand in hand.
Fabrico measures the equipment reliability and losses that determine how close to one-piece flow you can run. Flow is unforgiving of downtime — with no batch buffer, one machine's stoppage starves the next immediately — so Fabrico's live OEE and downtime data shows whether your equipment is reliable enough to sustain flow, and where the losses are that force you back to batching as a buffer. By improving the availability behind the scenes, it helps you move toward flow safely. Book a demo to see the reliability your flow depends on.
One-piece flow moves a single unit through each step before the next, one at a time. Batch production processes a group of units together at each step before moving the whole lot forward. One-piece flow cuts lead time and exposes problems; batching builds inventory and hides them.
Because moving single units slashes lead time (a unit waits for only one operation, not a whole batch at every step), minimises work-in-process inventory, and surfaces defects within a unit or two instead of across a whole lot. It attacks lead time, inventory, and hidden defects at once.
Yes. Batching can be justified where a step has a long, expensive changeover to amortise, where a process is inherently batch (ovens, baths, curing), or where distant or shared resources favour moving lots. The lean goal is to shrink batches toward one wherever feasible, not to ban them.
Balanced, reliable steps with short changeovers. Because there is no batch buffer, one machine's stoppage immediately starves the next, so flow depends on dependable equipment and a balanced line. Reducing changeover time via SMED is often what makes smaller batches and flow economic.
Flow surfaces quality and downtime losses immediately rather than hiding them in batched work-in-process, which drives OEE improvement. But flow only works on reliable equipment, so good OEE and high availability are prerequisites for sustaining one-piece flow.
Connexion
Blog
