YOKOTEN

YOKOTEN

Meaning

Means   “Across  Every where”

Yokoten is a Japanese word that roughly translates to “best practice sharing”.

Yokoten, the term Toyota adopted to capture the idea of horizontal transfer of information and knowledge across an organization.

Yokoten encourages sharing of data across the organization’

It is one of the winning behaviors of Toyota, namely copying and improving on KAIZEN™ idea that works. Toyota  calls this yokoten since it’s more precise than “copy” or “horizontal deployment” or “sideways expansion”.

It’s not a vertical (top-down) requirement to copy as Intel might deploy it in their “copy exactly” model. It’s not a “best practices” or benchmarking approach per se. Yokoten is horizontal, or more peer-to-peer, with the expectation that people will go & see it for themselves (this is called genchi gembutsu) and learn how another area did kaizen. In yokoten at Toyota there is an expectation that copying a good idea will be followed by some added KAIZEN™ to that idea.

How yokoten is done at Toyota?

Rather than waiting for the KAIZEN™ information to go up the chain of command where it can be sent back down to another area to copy or learn from, Toyota people are encouraged to go see for themselves, and return to their own area to add their own wisdom and ideas to the knowledge they gained.

The role of the senior managers is to make people aware of the existence of these good KAIZEN™ examples so that they can go see for themselves, gain the knowledge and improve upon it further

Simply telling subordinates to copy it may be KAIZEN™ of a sort but it would not serve the second important aspect of the Toyota Production System, the respect for and development of people.

Toyota has learned, it is not enough to copy (adopt) the result of good kaizen, we must also copy  (adopt) the thinking that resulted in the good KAIZEN™

Toyota Business Practice

Within the 8 step practical problem solving process known as TBP (Toyota Business Practice) the yokoten activity happens in step 8.

  1. Clarify the problem
  2. Break down the problem
  3. Set a target
  4. Analyze the root cause
  5. Develop countermeasures
  6. See countermeasures through
  7. Evaluate both results and process
  8. Standardize successes, learn from failures

Within the PDCA cycle yokoten happens in the Act (A) stage

How can we adopt it?

We can do “yokoten of yokoten” by studying Toyota and how they do it. They began 60 years ago when their managers and engineers traveled to the USA to learn from leading American manufacturers. At Toyota today the expectation is that KAIZEN™ is not complete until yokoten is confirmed and the learning is shared with others. Yokoten is part of the culture. It may not be too strong to say that it is a job requirement. KAIZEN™ must result in a standard, and yokoten means standards must be copied (studied, adapted & improved) by others. However it is not enough to copy (adopt) good KAIZEN™ as it is, one must adapt and improve the learning for one’s own process

Basic requirement of Yokoten

There is another Japanese phrase which is often associated with building a yokoten culture. It is kaze toushi ( 風通し ) and literally means “ventilation” or “wind blowing through” but refers to the openness or ease of communication within an organization. When this ventilation or information flow is poor, yokoten does not happen.

Why Yokoten?

Yokoten is a essential part of long-term success in a Lean culture, but can also have a big impact on short-term results. Yokoten is a success multiplier. Perform a good kaizen, and then copy (adopt) the results, learn from it & adopt it wherever applicable, and you immediately duplicate or multiply the impact.

The same is true of lean. There is no guarantee that it will continue on its own into the future. We need to exploit Yokoten to assure that we continue to be Lean into the future.

By

Mr.Mukesh Khare – Kaizen Institute India

Recent Posts

Daily Work Management and its Importance!
Economic Revival – Are we Ready?
Extracting Cash from Working Capital through Lean Distribution
 

arrow up