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 |  Decision Making Constraint Analysis |  Operations After-Action Review |  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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 | Low | High |
Timedifferent | 1-2 h | 30-90 min | 20-45 min | 2-4 h Analyse, laufend |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Lessons learned, Action items, Event summary | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ConstraintsDecisionPlanningOptions | LearningOperationsImprovement | OperationsConstraintsFlowImprovement |