Flow Kaizen

Flow kaizen is the higher-leverage cousin of point kaizen. Where point kaizen targets one workstation, flow kaizen targets the connections between workstations: how material moves, how information flows, where queues form, what each process is waiting for. Most of the biggest waste in a shop is not inside individual processes; it lives in the gaps between them. Flow kaizen is what addresses those gaps. It is also harder to execute and easier to bungle, which is why most shops should do many more point kaizens than flow kaizens.

"Polishing each station is satisfying. Fixing how parts move between them is where the lead time actually drops."

How flow kaizen works

Flow kaizen almost always starts with a value stream map of the current state. The map traces a product family from raw material to ship, showing each process, the cycle times, the queue lengths between processes, the inventory levels, and the information flows that trigger each step. The point of the map is to make the waste between processes visible. A typical first map reveals that 80 to 95 percent of total lead time is spent waiting, not making.

From the current-state map, the team proposes a future state. The future state usually involves changes like smaller batches, pull signals between steps replacing forecasts, queue limits that prevent inventory from accumulating, reorganized layout that shortens the path, or merged steps that eliminate handoffs. The future state is not a fantasy. It is a realistic target the team thinks is achievable in three to twelve months.

Then comes the work of getting from current state to future state. This is where flow kaizen separates from a map-making exercise. The transition is broken into a sequence of concrete projects, each with an owner, each tied to one specific change in the value stream. Some of those projects are small enough to look like point kaizens (move a bin, change a checklist). Others require coordinated effort across two or three teams (install kanban signals between mill and assembly, reduce setup on the brake so batches can shrink, renegotiate raw stock deliveries). The flow kaizen is the whole sequence, not any single project inside it.

The discipline that holds a flow kaizen together is acting on the map. Maps that get framed and hung on the wall are diagnostics that produced no improvement. Useful flow kaizens treat the future state as a commitment that gets executed in pieces over months.

Where flow kaizen fits on the shop floor

Imagine a 50-person fabrication shop where individual operations are running well after a year of point kaizens. Cycle times at each station have improved. Setups have come down. Quality at each station is acceptable. But lead time from order to ship is still six weeks, because parts sit in queues between processes for days at a time.

A flow kaizen would map the current state of the busiest product family. The map shows that of 30 working days lead time, only about three days are value-add. The rest is queue time. The future state targets 15 day lead time by installing kanban signals between three sets of operations, shrinking batch sizes on the brake from 200 to 50, and adding a daily release in shipping rather than a weekly batch.

The team executes the future state over four months in coordinated pieces. The setup-reduction work happens first, because shrinking batches depends on shorter setups. Then the kanban signals get installed and the brake operators learn to make to demand rather than forecast. Then shipping shifts to daily release. By month five, lead time is at 17 days and trending toward target. No single change did the work. The change is in how parts now move between processes.

Common mistakes with flow kaizen

• Mapping without acting. A current-state map is a diagnostic. A future-state map is a commitment. Without the execution, the maps are wasted work.
• Doing flow kaizen without the daily kaizen habit. Flow kaizen produces a sequence of changes that have to be executed and maintained. Shops without a daily improvement culture cannot sustain them.
• Trying to fix the whole value stream at once. Pick the section with the most obvious flow waste and do that section. Then pick the next.
• Ignoring the upstream constraint. Improving flow downstream of a real bottleneck just builds inventory at the bottleneck. Address the constraint first.
• Stopping at the map. The map is half the work. The other half is the months of small coordinated changes that bring the future state into being.

Flow kaizen and related Lean tools

Flow kaizen is the value-stream cousin of point kaizen. Both are types of kaizen, the daily continuous improvement habit. The diagnostic that almost always anchors a flow kaizen is value stream mapping, which exposes where parts wait and where information flows are broken. The target document the team works toward is a future-state map, a one-page picture of where the value stream should be in three to twelve months.