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 Learning Review | ![]() Operations Theory of Constraints |
|---|---|---|---|---|
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 a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 20-60 min | 1-3 h | 2-4 h Analyse, laufend |
Participantsdifferent | 3-8 | 1 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Plain-language Explanation, Knowledge Gaps, Study Notes | Learning Review Notes, System Factors, Improvement Actions | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowMeasurementConstraints | LearningKnowledgeUnderstanding | LearningRetrospectiveIncidentOperations | OperationsConstraintsFlowImprovement |



