Yokoten (Horizontal Deployment)
Yokoten means horizontal deployment of a practice that has already proven itself in one area. In lean manufacturing it is peer-to-peer learning: document a completed PDCA result, identify similar processes elsewhere, go see the source, adapt to local layout and people, measure the receiving site's own before and after, then update that site's standard work. It is stronger than emailing a best-practice deck because it insists on gemba and local ownership.
Plant teams care because multi-site programs often fail on the transfer step. Plant A cuts empty travel after a buffer move. Plant B copies the slide. Different layout, no shared before metric. Months later both argue that yokoten "does not work here." The missing piece was comparable spatial evidence, not motivation.
Multi-hall operational digital twins help when sites share naming and place-and-time measures so before pictures are comparable. Cost and governance of that visibility sit under multi-hall twin management. twinzo supports the evidence layer when sites already agree what empty travel, dwell, or aisle congestion means.
Key Components
Proven source PDCA: Measured result that met target and held, with root cause and exact change written down.
Candidate list: Similar lines, shifts, or plants selected by someone who sees across sites, with apply or skip reasons.
Go-see: Receiving team visits the source before changing its own floor.
Local baseline: The receiving site's own before metric, not only the source's story.
Close condition: Local after result plus updated standard work. Without the standard, drift returns.
Applications in Manufacturing and Logistics
Assembly plants deploy fixture or sequence changes across sister lines after one cell proves the gain. Logistics teams deploy buffer moves, milk-run pitch changes, or claim rules across halls when empty travel and dwell use the same definitions. Corporate CI offices use yokoten trackers to stop spreading unvalidated experiments and to include learning from failures, not only success slides.
Benefits and Challenges
Benefit: faster learning across the network without reinventing every countermeasure. Challenge: slide-only copy, unique local conditions ignored, and missing comparable metrics. Yokoten also fails when sites treat the map as finished Act and never rewrite local standard work.
Related Terms
Kaizen creates the improvement yokoten may spread. PDCA is the proof gate before deployment. Gemba is the go-see habit. Multi-site deployment is the program shape. An operational digital twin can supply comparable place-and-time evidence across halls.
Frequently Asked Questions
Is yokoten just best-practice sharing? Best-practice email is weaker. Yokoten requires go-see, adaptation, local measure, and standard update.
Should every kaizen be yokoten'd? No. Only proven PDCA results on processes that are similar enough elsewhere.
What if the receiving plant has a different layout? Adapt, do not paste. Comparable metrics still matter so teams know whether adaptation worked.
Where does twin evidence help? Shared spatial before and after pictures reduce invented baselines. See yokoten fails when every plant invents its own before picture.