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 Domain Storytelling |  Operations Bottleneck Analysis |  Knowledge Modeling Feynman Technique |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 1-2 h | 1-3 h | 20-60 min | 2-4 h Analyse, laufend |
Participantsdifferent | 2-8 | 3-8 | 1 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Plain-language Explanation, Knowledge Gaps, Study Notes | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | FlowMeasurementConstraints | LearningKnowledgeUnderstanding | OperationsConstraintsFlowImprovement |