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 |  Operations After-Action Review |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
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. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 2-4 h Analyse, laufend | 1-2 h | 20-45 min | 1-3 h |
Participantsdifferent | 3-12 | 1-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Concept Map, Relationship Labels, Knowledge Gaps | Lessons learned, Action items, Event summary | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | OperationsConstraintsFlowImprovement | KnowledgeConceptsMappingSensemaking | LearningOperationsImprovement | KnowledgeMappingRisk |