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 Domain Storytelling |  Knowledge Modeling Feynman Technique |  Operations Process Mapping |
|---|---|---|---|---|
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. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 2-4 h Analyse, laufend | 1-2 h | 20-60 min | 1-3 h |
Participantsdifferent | 3-12 | 2-8 | 1 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Domain Story, Glossary Notes, Process Narrative | Plain-language Explanation, Knowledge Gaps, Study Notes | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | OperationsConstraintsFlowImprovement | KnowledgeDomain-Driven DesignProcess | LearningKnowledgeUnderstanding | ProcessOperationsImprovement |