View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations PDCA Cycle |  Knowledge Modeling Domain Storytelling |  Operations After-Action Review |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1 h bis mehrere Wochen | 1-2 h | 20-45 min | 45-90 min |
Participantsdifferent | 1-8 | 2-8 | 3-12 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Domain Story, Glossary Notes, Process Narrative | Lessons learned, Action items, Event summary | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | Continuous improvementLeanExperiments | KnowledgeDomain-Driven DesignProcess | LearningOperationsImprovement | LeanProblem solvingCoachingOperations |