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 Feynman Technique |  Operations Theory of Constraints |  Operations Process Mapping |  Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | 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 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 20-60 min | 2-4 h Analyse, laufend | 1-3 h | 30-120 min |
Participantsdifferent | 1 | 3-12 | 3-10 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Constraint Map, Improvement Plan, Flow Metrics | Process Map, Handoff List, Improvement Backlog | Observation Notes, Improvement Ideas |
Tagsno overlap | LearningKnowledgeUnderstanding | OperationsConstraintsFlowImprovement | ProcessOperationsImprovement | LeanObservationProcessOperations |