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 | ![]() Architecture Architecture Decision Record | ![]() Delivery RAID Log |
|---|---|---|---|
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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-10 | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






