View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Architecture Request for Comments |  UX Design Customer Journey Canvas |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-2 Tage |
Participantsdifferent | 1-3 | 3-20 Reviewer | 3-10 | 1-4 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Customer Journey Canvas, Pain Points, Experience Opportunities | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | JourneyCustomerService designCanvas | ArchitectureDocumentationCommunication |