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 After-Action Review |  Operations Bottleneck Analysis |  Knowledge Modeling Knowledge Mapping |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 20-45 min | 1-3 h | 1-3 h | 20-60 min |
Participantsdifferent | 3-12 | 3-8 | 3-12 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Lessons learned, Action items, Event summary | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | LearningOperationsImprovement | FlowMeasurementConstraints | KnowledgeMappingRisk | LearningKnowledgeUnderstanding |