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 Event Modeling |  Systems Thinking Soft Systems Methodology |  Decision Making Red Teaming |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | 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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 2-6 h | 0.5-3 Tage | 1-4 h | 2-8 h |
Participantsdifferent | 2-8 | 5-15 | 3-8 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Challenge Findings, Risk Register, Mitigation Plan | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Soft systemsComplexitySensemakingSystems thinking | RiskDecisionSensemaking | Domain-Driven DesignEventsDiscoveryWorkshop |