Yokoten is the short for either Yokotenkai (横展開) or Yokoni Tenkaisuru.
Japanese kanjis are composed with irreductible parts named “radicals” and compositions of transformed radicals named “components”. They provide underlying concepts, just like a rebus.
Let’s decompose the underlying ideas in this Japanese writing from the components and radicals:
横 : sideways, side, horizontal, width, woof, unreasonable, perverse - it’s etymology is “across, as in a cross beam”, and its radicals are
- 木: wooden clappers (signaling the beginning or end of a performance)
- ハ : “wa” - 3rd music note / box / car / receptacle for feces / square guitar
- 田: rice field - this can be understood as the work place where wealth is grown
展 : unfold, expand / exhibition - it’s original meaning is to roll over in sleep, and then to unfold
開: open, unfold, unseal
The primitive character from Liushutong, two hands opening a gate can easily be seen:

clearly shows two hands opening a gate
From this in depth analysis, Yokoten can literally be understood as an invitation to open with both hands the doors to unveil dead bodies found in the workplace at the final clap, a postmortem.
To reveal the Yokoten power, this exchange of information should take place across different structures and hierarchies [Roser 2021] to spread information across the organization, on both the results and even more importantly the process, of how the results were achieved.
Yokoten helps is key for improvement or problem solving because it addresses systemic problems [Soltero 2017]; therefore, Yokoten is crucial for systemic improvement and may come in different flavors, such as retrospectives and demos at organization level.
Yokoten implies that improvement actions are not over until the return of lessons learnt have not been spread [Aimetti 2011].
Impact on the testing maturity
Yokoten cannot be a centralized top-down “standard”. Sharing is promoted rather than enforcing practices [Larman 2014]. This leads Managers to act as Landscape Gardeners who simply take care of seedlings and let them grow. Actually, “Rigid standards will only kill kaizen…” [Larman 2014] [Imai 2012].
Few Yokoten practices from Japanese culture:
- Nemawashi (根回し, making arrangements): this is an informal way to get support from coworkers and others before starting a project - this increases the chances of success of the project [Roser 2021]
- Tatakidai (叩き台, chopping block or springboard for discussion): reaching a consensus and informing others when the project is 80% complete in order to improve acceptance likelihood [Roser 2021]
- Ringi (稟議, decision making using a circular letter system to inform all superiors and workers): the “ringi” is the japanization of the English word for “ring”; in Japan, it helps decision making since an employee is able to make a proposal on a document that travels around the company across all stakeholders who approve or request modifications. After the approval of all lower management levels, the approval of the CEO is then a mere formality. Also called “ringi seido” or “ringi system” [Roser 2021]
- Asaichi (朝市, “Morning Market”): literally, “the first thing in the morning” [Imai 2012] - this usually takes place as a daily meeting with a commitment to never carry forward the same problem to the next day [Imai 2012]
- Nomu (飲む, drink, smoke, take): in Japan, meeting at afterworks, drinking and chatting informally is essential to learn things kept untold, the tacit knowledge [Nonaka 1995]; this is so important that in Japan, a term rose from the mixing of nomu and communication: “nominication” or “nommunication”
Some other Yokoten-like practices from the agile culture:
- Community of Practice
- Retrospectives (with escalation process) or Inspect & Adapt from SAFe [SAFe 2021-49]
- Liberating Structures: series of workshops at scale techniques [Lipmanowicz 2014]
- Tea-REX: Return of Experiences at tea time [Moustier 2020]
- 3 amigos
- Flying Mentors: Mentors should be spread across the organization to evenly raise it maturity [Moustier 2020]
- Daily Standup Meeting: Scrum introduces the DSM to raise alerts on the Sprint objectives [Schwaber 2020]
- X-Teams: Teams are enabled with networking and Ambassadors features [Ancona 2002] to increase the Team’s sharing and solving abilities notably thanks to broadcasting, influencing and conversing [Appelo 2010]
- Review Bazaar: demos are organized as a Science fair with visitors [Larman 2010]
- Event-Storming: Ideation engineering technique at organization level [Brandolini 2021]
- Impact Mapping: workshop to spot actors, impacts and deliverables from a goal [Adzic 2013]
- PanTesting
As these practices tend to push information through the organization, it is a passive way of preparing the Gemba from the learnings of the Yokoten.
When Yokoten is to be set in an organization, the usual development of yokoten-type communication mechanisms starts first within a single Team, then department and eventually between departments.
Agilitest’s standpoint on this practice
Click here to ask for the standpoint of Agilitest
Related cards
To go further
- [Adzic 2013]: Gojko Adzic - 2013 - “Impact Mapping” - isbn:9784798136707
- [Aimetti 2011] : Fabrice Aimetti - « Comment faire Yokoten ? » - 17/SEP/2011 - https://wikiagile.cesi.fr/index.php?title=Comment_faire_Yokoten_%3F
- [Ancona 2002] : Deborah Ancona, Henrik Bresman et Katrin Kaeufer - AVR 2002 - “The Comparative Advantage of X-Teams” - https://www.researchgate.net/publication/39322924
- [Appelo 2010] : Jurgen Appelo - « Management 3.0: Leading Agile Developers, Developing Agile Leaders » - Addison Wesley - 2010 - ISBN : 978-0321712479 - voir aussi https://fr.slideshare.net/jurgenappelo/agile-management-leading-teams-with-a-complex-mind/
- [Brandolini 2021] : Alberto Brandolini - “Introducing EventStorming” - http://leanpub.com/introducing_eventstorming
- [Imai 2012]: Masaaki Imai - 2012 - “Gemba Kaizen: A Commonsense Approach to a Continuous Improvement Strategy” - isbn:9780071790352
- [Larman 2010]: Craig Larman & Bas Vodde - 2010 - “Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development With Large-Scale Scrum” - isbn:9780321636409
- [Larman 2014]: Craig Larman & Bas Vodde - JUN 2014 - “Lean Primer” - https://www.leanprimer.com/downloads/lean_primer.pdf
- [Lipmanowicz 2014] : Henri Lipmanowicz & Keith McCandless - 2014 - “The Surprising Power of Liberating Structures: Simple Rules to Unleash a Culture of Innovation” - ISBN:9780615975306
- [Moustier 2020] : Christophe Moustier – OCT 2020 – « Conduite de tests agiles pour SAFe et LeSS » - ISBN : 978-2-409-02727-7
- [Nonaka 1995] : Ikujirō Nonaka - 1995 - “The knowledge-creating company” - https://archive.org/search.php?query=external-identifier%3A%22urn%3Alcp%3Aknowledgecreatin00nona%3Alcpdf%3A392fce22-3c38-4d4d-aff6-5b1370b4e1c4%22
- [Roser 2021]: Christoph Roser - c 2021 - “Glossary of Lean Production Related Terms” - https://www.allaboutlean.com/lean-glossary/
- [SAFe 2021-49]: SAFe - FEV 2021 - “Inspect and Adapt” - https://www.scaledagileframework.com/inspect-and-adapt/
- [Schwaber 2020] : Ken Schwaber et Jeff Sutherland - « Le Guide Définitif de Scrum : Les Règles de Jeu » - NOV 2020 - https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-French.pdf
- [Soltero 2017]: Conrad Soltero & Patrice Boutier - 2017 - “The 7 Kata: Toyota Kata, TWI, and Lean Training” - isbn:9781466570542