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 |  Operations Process Mapping |  Knowledge Modeling Feynman Technique |
|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 | High | Medium | Low |
Timedifferent | 2-4 h Analyse, laufend | 1-3 h | 20-60 min |
Participantsdifferent | 3-12 | 3-10 | 1 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Process Map, Handoff List, Improvement Backlog | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | OperationsConstraintsFlowImprovement | ProcessOperationsImprovement | LearningKnowledgeUnderstanding |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
