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 Theory of Constraints |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Domain Storytelling |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 2-4 h Analyse, laufend | 1-2 h | 1-2 h | 20-45 min |
Participantsdifferent | 3-12 | 1-8 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Concept Map, Relationship Labels, Knowledge Gaps | Domain Story, Glossary Notes, Process Narrative | Lessons learned, Action items, Event summary |
Tagsno overlap | OperationsConstraintsFlowImprovement | KnowledgeConceptsMappingSensemaking | KnowledgeDomain-Driven DesignProcess | LearningOperationsImprovement |