Yokoten is horizontal deployment of learning, improvements, and standards across similar processes so gains spread beyond the original team.
Definition
Yokoten is a Lean concept meaning horizontal deployment or sharing across. It is the deliberate spread of learning, countermeasures, standards, and improvements from one area to other relevant areas.
Yokoten is not blind copying. It requires understanding the principle behind the improvement and adapting it to local conditions.
History
Yokoten comes from Japanese Lean and Toyota practice, where learning from one problem or improvement is shared broadly to prevent recurrence and accelerate organizational learning.
When to Use
Use Yokoten after successful Kaizen, RCCA, safety improvements, quality escapes, equipment countermeasures, standard work improvements, or lessons learned that may apply to other products, lines, shifts, sites, or functions.
Step-by-Step
- Capture the problem, cause, countermeasure, and evidence of effectiveness.
- Identify similar processes, equipment, products, or teams that may share the risk or opportunity.
- Explain the principle, not just the local solution.
- Review fit with receiving teams and adapt as needed.
- Assign owners, timing, and verification criteria for deployment.
- Update standards, training, FMEA, control plans, or checklists.
- Verify adoption and results across locations.
- Build learning into daily management and knowledge systems.
Examples
- Quality: A mistake-proofing fix from one line is evaluated on all similar lines.
- Safety: A near-miss countermeasure is shared across plants with similar equipment.
- Maintenance: A chronic failure lesson is added to PM standards for similar assets.
Common Pitfalls
- Copying a solution without understanding local conditions.
- No evidence that the original countermeasure worked.
- Lessons learned stored but not deployed.
- No owner for horizontal rollout.
- Forgetting to update standards and training.
- Assuming communication equals adoption.