View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Storytelling |  UX Research Customer Journey Mapping |  Architecture Architecture Decision Record |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 45-120 min | 2-4 h | 15-45 min | 60-90 min |
Participantsdifferent | 1-6 | 4-10 | 1-3 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Narrative Outline, Key Message, Story Arc | Journey Map, Pain-point List, Opportunity Backlog | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class |
Tagsno overlap | CommunicationNarrativeStakeholdersFacilitation | JourneyServiceService design | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance |