Kaizen on the line vs kaizen in internal logistics
The kaizen board is full of station ideas: tool reach, changeover steps, defect counters. The aisle that feeds those stations still burns empty travel nobody owns. Production looks lean. Internal logistics still runs on radio and hope.
Same method, different objects
Kaizen on the line and kaizen in logistics share PDCA, the three Ms, and ownership close to the work. What changes is the object under study. On the line the object is the station cycle, the quality outcome, and the operator motion inside a few metres (feet). In internal logistics the object is the move between places: loaded and empty paths, buffer dwell, milk-run intervals, and the handoff between operator and driver.
Lean already names transportation and motion as wastes. Plants often measure them carefully at the station and loosely in the aisle. Industry 4.0 continuous data closes that gap when movers and material become as observable as machine cycles. The culture baseline is still what kaizen is before the sensors arrive.
How the three Ms show up in each domain
Muda on the line includes rework, waiting for parts, and unnecessary walking inside the cell. In logistics it includes empty travel, search time, and double handling. Mura on the line is uneven station loads. In logistics it is hot and quiet loops on the same hall, or every line calling material at the same clock time. Muri on the line is an unsustainable takt. In logistics it is a few trucks absorbing every urgent move while averages still look calm.
Case studies of milk-run improvement with PDCA in automotive plants show the logistics side in practice: stratify supply, reverse logistics, and movement, then standardize routes and visual management. The method looks like production kaizen. The measures are cycle time of the train, travel waste, and material availability at the line.
What continuous measurement changes for each side
Line kaizen already often has cycle counters, andon history, and quality logs. Logistics kaizen historically depended on stopwatch studies and short gemba windows. Continuous location and transaction data let logistics Check look more like production Check: before and after on the same shift type, with paths and dwell instead of only completed moves in WMS.
That does not merge the two boards into one. It lets them talk. A station kaizen that cuts local walking can raise logistics muda if the new kit size doubles trip count. A logistics kaizen that thins the fleet can create muri on the remaining drivers and starve the stations the production board thought it had fixed. Cross-hall pattern work on a shared spatial record is how those interactions become visible. Faster PDCA with continuous evidence is described in how continuous measurement changes the kaizen loop.
How teams run both without stealing each other's wins
1. Keep separate owners, shared waste language - Production owns station standards. Logistics owns move standards. Both use muda, mura, and muri in the same meeting.
2. Pick measures that match the object - Cycle and defect for the line. Travel, dwell, and on-time material for logistics. Do not judge a milk-run trial with OEE alone.
3. Check side effects across the interface - After a line change, look at trip count and starve risk. After a logistics change, look at station waiting.
4. Treat visibility as the logistics prerequisite - Automating a chaotic aisle freezes chaos. Why visibility comes before automation in Industry 4.0 logistics is the next concept: lean logistics under Industry 4.0 is visibility before automation.
Internal logistics optimization work that uses live hall context sits under internal logistics optimization. Get in touch if you want production and logistics kaizen to share measures without merging ownership.