View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Customer Journey Mapping | ![]() Decision Making Delphi Method | ![]() Domain Modeling Context Map | ![]() UX Design Customer Journey Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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 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 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 | 2-4 h | 1-4 Wochen | 1-3 h | 1-3 h |
Participantsdifferent | 4-10 | 6-30 Experten | 2-8 | 3-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Expert Forecast, Consensus Range, Assumption Notes | Context Map, Integration Patterns, Boundary Notes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | JourneyServiceService design | ForecastingExpertsDecisionStrategy | Domain-Driven DesignBoundariesStrategy | JourneyCustomerService designCanvas |



