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 A3 Problem Solving | ![]() Knowledge Modeling Event Modeling | ![]() 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 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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 | Medium | Medium | Medium |
Timedifferent | 1-2 h | 45-90 min | 2-6 h | 0.5-5 Tage |
Participantsdifferent | 2-8 | 2-5 | 2-8 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | A3 Report, Action Plan, Root Cause Analysis | Event Model, UI Flow, Commands, Read Models | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | LeanProblem solvingCoachingOperations | EventsBlueprintDomain-Driven DesignBehavior | LeanContinuous improvementOperations |



