Continuous Flow and Pull System
Eliminate waste by making work flow one piece at a time
The Continuous Flow and Pull System combines Toyota's Principles 2 and 3 into a unified approach for designing work. Instead of processing work in large batches where items sit idle between steps, you redesign processes so each unit of work moves continuously from one step to the next without waiting. When continuous flow is not possible, you use pull systems (kanban) to limit work-in-process and prevent overproduction.
The power of this approach is not efficiency but visibility. When you reduce batch sizes toward one-piece flow, every problem becomes immediately apparent because there is no inventory buffer to hide behind. A quality defect, a supply delay, or a capacity imbalance stops the entire flow, forcing immediate resolution. This is uncomfortable but transformative.
To make flow work, you must also level the workload (heijunka). Rather than processing whatever comes in first-come-first-served, you sequence different types of work evenly throughout the day or week. This prevents the chaos of peak-and-valley demand patterns and creates the stability needed for continuous improvement.
- One-piece flow is the ideal state; every deviation from it is an opportunity to improve
- Pull systems prevent overproduction, which Toyota considers the worst form of waste
- Leveling workload (heijunka) creates the stability that makes flow possible
- Problems surfaced by flow are gifts, not interruptions
- Reducing inventory is a means of exposing problems, not an end in itself
- Map Your Current Value StreamDocument every step in your process from request to delivery. Identify where work sits idle, where batches accumulate, and where handoffs create delays. Calculate the ratio of value-added time to total lead time.Pro tipIn most organizations, value-added time is less than 5% of total lead time. The other 95% is waiting, batching, and rework.
- Create a Model Flow CellSelect one value stream and redesign it for continuous flow. Arrange work steps in sequence, eliminate unnecessary handoffs, and cross-train team members to handle multiple steps. Aim for the smallest batch size feasible.Pro tipToyota arranges physical workstations in a U-shape so one worker can manage multiple steps and the first and last steps are close together for easy rebalancing.WarningExpect problems to surface immediately. This is the point. Have support resources ready to resolve issues quickly.
- Implement Pull Signals Between StepsWhere true one-piece flow is not possible, install pull systems. Use kanban cards, designated buffer spaces, or digital signals so upstream steps only produce when downstream steps signal they are ready. Set work-in-process limits.Pro tipStart with larger buffers between steps and gradually reduce them. Each reduction will surface the next layer of problems to solve.
- Level the WorkloadInstead of processing whatever arrives in whatever order, create a leveled schedule that mixes different types of work throughout each period. This prevents peaks and valleys that overwhelm some steps while starving others.Pro tipToyota calls leveling heijunka and considers it the foundation that makes flow and pull possible. Without it, flow breaks down under demand variability.WarningLeveling requires discipline. Teams will resist scheduling constraints, preferring to batch similar work together for perceived efficiency.
- Build a Culture of Stopping to FixInstall andon systems that allow any team member to signal a problem and stop the flow. When flow stops, respond immediately with root cause analysis rather than workarounds. Standardize the fix and resume.Pro tipToyota's andon cord is pulled thousands of times per day. Most problems are resolved within the takt time without actually stopping the line. The key is the culture of empowerment.WarningIf management punishes people for stopping flow to fix problems, the system will fail. People will hide problems instead of surfacing them.
At Toyota's Georgetown, Kentucky plant, the assembly line implements one-piece flow where each vehicle moves through hundreds of workstations at a fixed takt time. Team members can pull an andon cord to signal problems. The most useful management metric was not output or cost but the number of andon pulls per department, which revealed exactly where problems were occurring.
Toyota's Hebron, Kentucky parts distribution center applied flow thinking to warehouse operations. They mapped the value stream for order fulfillment, identified that parts were being batched and sorted multiple times, and redesigned the process for more continuous flow from receiving to shipping.
Taiichi Ohno developed the Toyota Production System by studying American supermarkets in the 1950s. He observed that shelves were restocked only when customers pulled items off them, rather than being pushed full based on production schedules. He adapted this insight into kanban cards that signaled upstream processes to produce only what downstream processes had consumed.
The original experiments in 1947 met fierce resistance from workers who did not want to operate multiple machines. Ohno decided to be patient rather than force rapid change, letting the benefits of the system speak for themselves over time.