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 Teach-back |  Agile Sprint Retrospective |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
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. | 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 5-20 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-60 min |
Participantsdifferent | 3-8 | 2-8 | Scrum Team | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Understanding Check, Clarification Notes, Learning Gaps | Improvement actions, Team agreements | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | FlowMeasurementConstraints | LearningUnderstandingCommunication | RetrospectiveImprovementLearning | LearningKnowledgeUnderstanding |