Single-piece flow
Also known as One-piece flow, One-at-a-time flow
Definition
Single-piece flow is a process pattern in which work advances individually or in very small units through the value stream. It aims to expose problems early and reduce the waiting created by large batches.
Let one slice reveal the next problem
Single-piece flow reduces the amount of work waiting for a batch to finish before the next stage can begin. The goal is not literal serialization of every action. It is to move coherent, testable slices early enough that queues and defects become visible sooner.
A concrete example
An illustrative team changes a shared interface in four deployable steps. Each step is reviewed and validated before the next is pulled. The first slice reveals an integration issue while the change is still narrow, instead of after a month-long batch reaches testing.
Use the pattern selectively
Identify work that can be safely sliced, then compare cycle time, rework, and review effort before and after. Keep a larger batch when a migration or transaction requires atomic coordination, but make the reason explicit.
Limitations
Splitting work can increase coordination or create partially useful states. A tiny change is not automatically valuable or easier to understand. Optimize for coherent flow and safe feedback, not for the smallest possible card.
How this relates to Weave
Weave can help teams inspect change size, review waiting, and delivery timing when evaluating a small-batch experiment. It cannot determine whether a change is safely separable, so engineers must design coherent slices and protect quality controls.
Explore Engineering intelligence