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 Theory of Constraints |  Operations After-Action Review |  Operations Gemba Walk |
|---|---|---|---|---|
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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 1-2 h | 2-4 h Analyse, laufend | 20-45 min | 30-120 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary | Observation Notes, Improvement Ideas |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | OperationsConstraintsFlowImprovement | LearningOperationsImprovement | LeanObservationProcessOperations |