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 Bottleneck Analysis |  Knowledge Modeling Domain Storytelling |  Operations After-Action Review |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-2 h | 20-45 min | 20-60 min |
Participantsdifferent | 3-8 | 2-8 | 3-12 | 1 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Domain Story, Glossary Notes, Process Narrative | Lessons learned, Action items, Event summary | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | FlowMeasurementConstraints | KnowledgeDomain-Driven DesignProcess | LearningOperationsImprovement | LearningKnowledgeUnderstanding |