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 | ![]() Systems Thinking Evaporating Cloud | ![]() Product Strategy DIBB | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 60-120 min | 1-2 h | 45-90 min |
Participantsdifferent | 3-10 | 2-8 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | DIBB document, Belief list, Bet list, Learning report | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | JourneyCustomerService designCanvas | Theory of ConstraintsAssumptionsSystems thinking | StrategyDecisionAssumptionsHypothesis | ChangeDecisionStrategy |



