View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Domain Storytelling | ![]() Operations PDCA Cycle | ![]() Operations After-Action Review | ![]() Operations Kaizen Event |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 h | 1 h bis mehrere Wochen | 20-45 min | 0.5-5 Tage |
Participantsdifferent | 2-8 | 1-8 | 3-12 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Lessons learned, Action items, Event summary | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Continuous improvementLeanExperiments | LearningOperationsImprovement | LeanContinuous improvementOperations |



