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 Concept Mapping |  Operations Theory of Constraints |  Operations After-Action Review |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | High | Low | Low |
Timedifferent | 1-2 h | 2-4 h Analyse, laufend | 20-45 min | 20-60 min |
Participantsdifferent | 1-8 | 3-12 | 3-12 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | OperationsConstraintsFlowImprovement | LearningOperationsImprovement | LearningKnowledgeUnderstanding |