
Yokoten: Best Practice Sharing from a success
Last updated: December 04, 2022 Read in fullscreen view



- 01 Apr 2022
Ishikawa (fishbone) diagram in software project management 2076
- 24 Nov 2022
Genba Genbutsu Genjitsu (3Gs), (Go to the Genba & see for yourself!) 1857
- 09 Sep 2022
Kaizen, Kaikaku and Kakushin – what’s the difference? 1830
- 02 Nov 2021
What is Terms of Reference (ToR)? 1001
- 18 Oct 2021
Key Elements to Ramping Up a Large Team 820
- 03 Apr 2022
Microsoft Solutions Framework (MSF) 780
- 01 Oct 2020
Fail fast, learn faster with Agile methodology 695
- 10 Nov 2021
5S methodology - the SECRET to Japanese SUCCESS 661
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 642
- 19 Oct 2021
Software development life cycles 584
- 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 577
- 03 Jan 2024
What is the Ringi process? 552
- 20 Jul 2022
Software Myths and Realities 537
- 09 Sep 2022
What is 5 Whys (Five Whys)? 530
- 19 Oct 2021
Is gold plating good or bad in project management? 521
- 13 Jul 2022
Applying the business mantra "HORENSO" to Achieve 360-degree Communication 519
- 13 Apr 2024
Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 515
- 17 Mar 2023
Reduce waste in software development with 3M model: Muda, Mura, Muri 494
- 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 493
- 02 May 2022
What Is RAID in Project Management? (With Pros and Cons) 476
- 01 Jan 2023
How To Use Poka-Yoke (Mistake Proofing) Technique To Improve Software Quality 464
- 15 Jul 2022
Hansei Methodology: Continuously Engaging People in Improvement 461
- 01 Dec 2023
What is Amoeba Management? 456
- 13 Jan 2020
Quiz: Test your understanding project cost management 455
- 08 Oct 2022
KPI - The New Leadership 444
- 29 Aug 2022
Difference between Kaizen and Innovation 422
- 28 Jul 2022
POC, Prototypes, Pilots and MVP: What's the differences? 421
- 15 Apr 2022
Total Quality Management (TQM) - Japanese-style management approach to quality improvement. 410
- 14 Jun 2022
Example and Excel template of a RACI chart in Software Development 406
- 18 Dec 2023
The Cone of Uncertainty in Scrum & Requirement Definition 405
- 01 Mar 2022
The Toyota Way Management Principles 384
- 27 Jan 2020
Should a project manager push developers to work more hours due to mistakes of manager schedule setting? 362
- 18 Jul 2021
How To Ramp Up An Offshore Software Development Team Quickly 359
- 12 Oct 2022
14 Common Reasons Software Projects Fail (And How To Avoid Them) 348
- 06 Jun 2022
HEIJUNKA: The art of leveling production 344
- 27 Aug 2022
Kaizen - Culture of Continuous Improvement and Lean Thinking 342
- 19 Sep 2022
Jidoka in Software Development and Odoo ERP/MRP 329
- 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 300
- 28 Oct 2022
Build Operate Transfer (B.O.T) Model in Software Outsourcing 290
- 13 Oct 2021
Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 279
- 12 Aug 2022
What is End-to-end project management? 275
- 03 Jan 2023
Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) 270
- 05 Mar 2021
How do you minimize risks when you outsource software development? 270
- 17 Oct 2021
Does Fast Tracking increase project cost? 259
- 07 Jul 2022
Managing Project Execution Terms 257
- 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 254
- 12 Dec 2021
Zero Sum Games Agile vs. Waterfall Project Management Methods 254
- 28 Dec 2021
8 types of pricing models in software development outsourcing 252
- 19 Apr 2021
7 Most Common Time-Wasters For Software Development 250
- 09 May 2022
Build one to throw away vs Second-system effect: What are differences? 245
- 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 241
- 02 Nov 2023
Unlocking Success with The Amoeba Management Model: Key Lessons, Pros & Cons, and Finding the Perfect Fit 238
- 13 Dec 2020
Move fast, fail fast, fail-safe 237
- 31 Oct 2021
Tips to Fail Fast With Outsourcing 228
- 26 Sep 2024
Successful Project Management Techniques You Need to Look Out For 223
- 06 Jun 2022
Change Management at the Project Level 221
- 06 Feb 2021
Why fail fast and learn fast? 217
- 22 May 2022
What are common mistakes that new or inexperienced managers make? 212
- 04 Oct 2021
Product Validation: The Key to Developing the Best Product Possible 198
- 06 Nov 2019
How to Access Software Project Size? 192
- 01 Jun 2020
Japan Business Review (JBR) 190
- 04 Oct 2022
Which ERP implementation strategy is right for your business? 188
- 18 Aug 2022
What are the consequences of poor requirements with software development projects? 183
- 15 May 2022
20 Common Mistakes Made by New or Inexperienced Project Managers 179
- 01 Aug 2022
Is planning "set it and forget it" or "set it and check it"? 174
- 12 Mar 2022
The u-Japan concept 172
- 31 Aug 2022
What are the best practices for software contract negotiations? 166
- 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 164
- 02 Dec 2021
3 Ways to Avoid Scope Creep in IT Consulting 150
- 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 136
- 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 129
- 01 Mar 2023
Bug Prioritization - What are the 5 levels of priority? 129
- 04 Mar 2024
Tree Ring Management: Take the Long Term View and Grow Your Business Slowly 126
- 10 Apr 2024
The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 124
- 10 May 2022
Levels of Teamwork 116
- 07 Dec 2023
12 project management myths to avoid 113
- 05 Sep 2023
The Cold Start Problem: How to Start and Scale Network Effects 107
- 01 May 2024
Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 107
- 02 Jun 2024
Reviving Ancient Wisdom: The Spiritual Side of Project Management 106
- 24 Nov 2023
The project management paradox: Achieving MORE by doing LESS 101
- 30 Nov 2023
Project Managers, Focus on Outcomes — Not Deliverables 99
- 05 Jan 2024
Easy ASANA tips & tricks for you and your team 93
- 02 Nov 2022
Difference between Change Management and Project Management 89
- 21 Jun 2024
Dead Horses and the Escalation of Commitment 84
- 06 Mar 2024
[SemRush] What Are LSI Keywords & Why They Don‘t Matter 84
- 05 Jun 2023
Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 76
- 01 Dec 2023
Laws of Project Management 76
- 12 Mar 2024
How do you create FOMO in software prospects? 63
- 23 Jun 2024
Best Practices for Managing Project Escalations 54
- 14 Mar 2024
Why should you opt for software localization from a professional agency? 51
- 01 Mar 2024
10 Project Management Myths 47
- 12 Aug 2024
Understanding Google Analytics in Mumbai: A Beginner's Guide 37
What is Yokoten?
Yokoten means “horizontal deployment”. It refers to the practice of copying good results of kaizen in one area to other areas. Yokoten applies more broadly to copying product design ideas as well as better practices in general.
“Best practice sharing” comes close to the meaning of yokoten. In modern business that phrase often means e-mailing PowerPoint presentations, comparing results between divisions and debating the differences between various round fruits.
In project management, Yokoten is a Japanese manufacturing concept that is especially relevant to Project Managers. Yokoten means 'Best Practice Sharing'.
Yoko: Sideways
Tenkai: Development
It's the best translation of a term adopted by Toyota. It reflects the idea of transferring ideas and information among peers.
Yokoten builds on another, more familiar concept: 'Kaizen'
Kaizen is a continuous flow of improvements. Everyone on your team has the right - and responsibility - to spot ways to do things better.
Once you find an idea that works, through Kaizen, the next thing to do is to share it. That's Yokoten. In Toyota's usage, it carries the ideas of:
- sharing a new idea
- transmitting it across the organization (rather than top-down)
- allowing others to copy it
- co-operation between teams
- a shared sense of responsibility and success
Yokoten binds teams and work-groups together into a larger team. For Toyota, it has a big impact on results. It is a 'success-multiplier'.
Where does Yokoten Happen within the Problem Solving Cycle?
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, corresponding to step 8 above.
Lesson Learned Meetings are not Enough
Your team members could go further. Encourage them to share new discoveries among themselves. Give them permission to see what other team members are doing.
Your role is to encourage this and get the word out. Simply copelling people to copy innovations and improvements is a step. But for sustainable personal growth and team performance improvements, you need more.
It's attitudes and thinking that people need to share, copy, and adopt. We only really learn lessons when we adopt new ideas and the thinking behind them.
Why Are We Slow to Copy Good Practices through Yokoten?
Yokoten is an 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 copy the results, and you immediately duplicate the impact. Yet we don’t hear so much about yokoten. Why is this? In a typical company the best practices can become lost among the noise, buried beneath the day-to-day fire-fighting or even deliberately hidden from others in to make one’s own self or group look good. There may be localized incentives in place that prevent yokoten from happening. There are other obstacles to yokoten, including a lack of documented standard as a result of kaizen, weak “go see” culture, or no metrics or ways to agree on what is in fact a better practice.
Via Internet
