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 Bottleneck Analysis |  Domain Modeling EventStorming |  Decision Making Constraint Analysis |  Knowledge Modeling Event Modeling |
|---|---|---|---|---|
Purposedifferent | 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. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 2-8 h | 30-90 min | 2-6 h |
Participantsdifferent | 3-8 | 5-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | FlowMeasurementConstraints | Domain-Driven DesignEventsDiscoveryWorkshop | ConstraintsDecisionPlanningOptions | EventsBlueprintDomain-Driven DesignBehavior |