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 ABC Analysis | ![]() 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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 | Low | High |
Timedifferent | 1-2 h | 30-60 min | 2-4 h Analyse, laufend |
Participantsdifferent | 2-8 | 1-5 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | ABC Classification, Focus Rules, Control List | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | PrioritizationOperationsPortfolio | OperationsConstraintsFlowImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






