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 |  Knowledge Modeling Feynman Technique |  Operations After-Action Review |
|---|---|---|---|---|
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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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 | Low | High | Low | Low |
Timedifferent | 1-2 h | 2-4 h Analyse, laufend | 20-60 min | 20-45 min |
Participantsdifferent | 2-8 | 3-12 | 1 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Constraint Map, Improvement Plan, Flow Metrics | Plain-language Explanation, Knowledge Gaps, Study Notes | Lessons learned, Action items, Event summary |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | OperationsConstraintsFlowImprovement | LearningKnowledgeUnderstanding | LearningOperationsImprovement |