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 Design Customer Journey Canvas | ![]() Domain Modeling Context Map | ![]() Decision Making Force Field Analysis | ![]() Decision Making Delphi Method |
|---|---|---|---|---|
Purposedifferent | 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 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 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 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 | Low | High |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 1-4 Wochen |
Participantsdifferent | 3-10 | 2-8 | 3-12 | 6-30 Experten |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | JourneyCustomerService designCanvas | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy | ForecastingExpertsDecisionStrategy |



