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 Teach-back | ![]() Operations Theory of Constraints | ![]() Knowledge Modeling Feynman Technique | ![]() Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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. | 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. | 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. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 5-20 min | 2-4 h Analyse, laufend | 20-60 min | 1-3 h |
Participantsdifferent | 2-8 | 3-12 | 1 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Constraint Map, Improvement Plan, Flow Metrics | Plain-language Explanation, Knowledge Gaps, Study Notes | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | LearningUnderstandingCommunication | OperationsConstraintsFlowImprovement | LearningKnowledgeUnderstanding | FlowMeasurementConstraints |



