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 Delphi Method | ![]() UX Research Customer Journey Mapping | ![]() UX Design Customer Journey Canvas |
|---|---|---|---|---|
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. | 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. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 2-4 h | 1-3 h |
Participantsdifferent | 2-8 | 6-30 Experten | 4-10 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes | Journey Map, Pain-point List, Opportunity Backlog | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy | JourneyServiceService design | JourneyCustomerService designCanvas |



