feat: expand seed library from 6 to 100 protocols
Added 94 new protocol YAML seed files covering diverse global cultures and practices: Indigenous & traditional: Maori powhiri, Aboriginal yarning, Somali xeer, Moroccan jmaa, Tswana kgotla, Zulu imbizo, Peruvian ronda campesina, Ohlone land-back, Inuit IQ consensus, Haudenosaunee condolence, Navajo peacemaking, Ojibwe pipe ceremony, Polynesian talanoa, Rwandan gacaca, West African palaver tree, Mexican tequio, Javanese musyawarah-mufakat, Tibetan story council, Korean yangban, Filipino utari, Ainu practices Religious communities: Quaker meeting for business, clearness committee, Amish shunning (Meidung), Mennonite discernment, Jewish hevruta, Rastafari nyabinghi reasoning Facilitation: World Cafe, Open Space, Future Search, Six Thinking Hats, Dynamic Facilitation, Socratic Seminar, Delphi method, Copenhagen Consensus, Lean Coffee, Hackathon sprint, Agile retrospective, Stand-up meeting, Pair programming, Roadmap planning Governance: Sociocratic consent selection, Dynamic self-governance, Cooperative consensus, Hackerspace consensus, Mastodon governance, Climate assemblies (x2), Basque asamblearismo Conflict & repair: Restorative conference, circle sentencing, Nonviolent Communication (3 protocols), Active listening mirror, Appreciative apology repair Community & care: Community kitchen, Gratefulness circle, Passing circle, Paired walking, Deep listening dyad, Mutual aid, Permaculture charrette Education: Barefoot College night school, Socratic seminar Everyday: Various greeting, transition, and gratitude protocols All protocols credit original sources. Cultural context noted in descriptions. All YAML files validated.
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
id: japanese-kaizen-retrospective
|
||||
title: Kaizen Retrospective
|
||||
description: >-
|
||||
A continuous improvement meeting pattern from Japanese manufacturing
|
||||
practice, used by teams to surface small changes that improve the work.
|
||||
Originating in the Toyota Production System kaizen tradition.
|
||||
source: Toyota Production System / Lean Enterprise Institute
|
||||
source_url: https://www.lean.org/
|
||||
tags: [kaizen, retrospective, lean, teams]
|
||||
forked_from: null
|
||||
image: null
|
||||
steps:
|
||||
- headline: Define the standard
|
||||
description: >-
|
||||
The team reviews the current standard work — what the process is
|
||||
supposed to be — so everyone shares the baseline.
|
||||
- headline: Find the gap
|
||||
description: >-
|
||||
Each member names one place where the actual work differs from the
|
||||
standard, focusing on the work, not the worker.
|
||||
- headline: Ask five whys
|
||||
description: >-
|
||||
For one chosen gap, the group asks "why?" repeatedly until they reach
|
||||
a root cause, not just a symptom.
|
||||
- headline: Propose a small change
|
||||
description: >-
|
||||
The team proposes the smallest possible change that addresses the root
|
||||
cause, with an owner and a trial period.
|
||||
- headline: Update the standard
|
||||
description: >-
|
||||
After the trial, the team decides whether to adopt the change and
|
||||
updates the written standard work.
|
||||
outcome: >-
|
||||
A specific, tested improvement is adopted and the standard work is updated;
|
||||
the team builds a habit of continuous small improvements.
|
||||
practice: >-
|
||||
Resist big redesigns. Kaizen favours many small changes over grand
|
||||
overhauls. Keep the five whys honest — stop at the first answer the team
|
||||
can act on.
|
||||
Reference in New Issue
Block a user