View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Decision Making OODA Loop |  UX Design Customer Journey Canvas |  Decision Making Delphi Method |
|---|---|---|---|---|
Purposedifferent | 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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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 | Medium | Medium | High |
Timedifferent | 1-3 h | 15-60 min je Zyklus | 1-3 h | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-8 | 3-10 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Situation Assessment, Decision Loop, Action Updates | Customer Journey Canvas, Pain Points, Experience Opportunities | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | DecisionChangeLearningStrategy | JourneyCustomerService designCanvas | ForecastingExpertsDecisionStrategy |