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 Design Customer Journey Canvas |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 45-120 min | 1-3 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 1-6 | 3-10 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Narrative Outline, Key Message, Story Arc | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | CommunicationNarrativeStakeholdersFacilitation | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |