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