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 |  Decision Making Force Field Analysis |  Domain Modeling Context Map |  Decision Making Delphi Method |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 2-6 h | 45-90 min | 1-3 h | 1-4 Wochen |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Force Field Map, Change Levers, Risk Notes | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ChangeDecisionStrategy | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy |