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 Bottleneck Analysis |  Agile Sprint Retrospective |  Operations Theory of Constraints |
|---|---|---|---|---|
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 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. | 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. | 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 | Low | Medium | Low | High |
Timedifferent | 5-20 min | 1-3 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 2-4 h Analyse, laufend |
Participantsdifferent | 2-8 | 3-8 | Scrum Team | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Improvement actions, Team agreements | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | LearningUnderstandingCommunication | FlowMeasurementConstraints | RetrospectiveImprovementLearning | OperationsConstraintsFlowImprovement |