Yokoten is a Japanese term commonly used in Lean to describe horizontal sharing of learning across an organization.

When one team solves a problem or develops a better method, the learning may be relevant elsewhere.

Yokoten creates a deliberate way to spread that learning.

It is not simply copying a solution from one area to another.

Share the learning, not only the answer

A team receiving an improvement should understand:

  • what problem existed;
  • what causes were found;
  • what countermeasure was tested;
  • what result changed;
  • what conditions made the solution work.

That context matters.

A fixture that works on one machine may not fit another process with different tolerances, product mix, or risk.

Start with verified improvement

Do not spread an idea before the result is understood.

Use PDCA to test the change and confirm whether it produced the expected effect.

Once the learning is stable enough to share, document the important conditions rather than only the final design.

Look for similar processes

Potential receiving areas may share:

  • the same equipment;
  • the same defect mode;
  • similar material flow;
  • common work content;
  • common suppliers;
  • common customer requirements.

The goal is to find where the learning has a plausible application.

Adapt locally

Yokoten should encourage adaptation.

The receiving team should evaluate:

  • local risks;
  • process differences;
  • layout;
  • demand;
  • equipment;
  • standards;
  • workforce needs.

Standard Work should be updated only after the local version is tested and verified.

Use visual examples

Before-and-after photos, short problem summaries, A3s, diagrams, and simple videos can make learning easier to transfer.

A3 Problem Solving can provide a compact narrative of the problem, analysis, countermeasures, and result.

Avoid central mandates

If leadership says, “Site A did this, so every site must copy it,” teams may install solutions that do not fit.

A better instruction is:

Review this learning. Determine whether the problem exists here. Test the applicable parts and adapt them to local conditions.

That preserves learning while respecting process differences.

Make sharing routine

Yokoten can be built into:

  • kaizen reviews;
  • engineering meetings;
  • maintenance forums;
  • quality councils;
  • leader standard work;
  • cross-site communities.

The organization should not depend on accidental conversations for knowledge transfer.

Common mistakes

Sharing solutions before they are verified, copying without understanding conditions, forcing every area to use the same countermeasure, documenting only the result rather than the reasoning, and failing to track whether transferred learning actually helped are common mistakes.

Practical sequence

  1. verify the original improvement.
  2. document the problem and learning.
  3. identify potentially similar processes.
  4. share the reasoning and evidence.
  5. let receiving teams assess applicability.
  6. test the idea locally.
  7. adapt where needed.
  8. update local standards after verification.
  9. share the local result back.
  10. continue spreading useful learning.

The practical lesson

Yokoten multiplies improvement by moving learning horizontally.

The organization gains more value from one solved problem when other teams can understand, test, and adapt the lesson.