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 Request for Comments |  Decision Making Argument Mapping |  UX Design Customer Journey Canvas |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-3 h | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 3-10 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance |