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 Theory of Constraints |  Knowledge Modeling Feynman Technique |  Agile Sprint Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 2-4 h Analyse, laufend | 20-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 3-12 | 1 | Scrum Team | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Plain-language Explanation, Knowledge Gaps, Study Notes | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tagsno overlap | OperationsConstraintsFlowImprovement | LearningKnowledgeUnderstanding | RetrospectiveImprovementLearning | LearningOperationsImprovement |