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 Bottleneck Analysis |  Operations Process Mapping |  Operations After-Action Review |
|---|---|---|---|---|
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 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 h | 1-3 h | 20-45 min |
Participantsdifferent | 1-8 | 3-8 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Process Map, Handoff List, Improvement Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | FlowMeasurementConstraints | ProcessOperationsImprovement | LearningOperationsImprovement |