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 |  Architecture Software Architecture Canvas |  UX Design Customer Journey Canvas |
|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 3-10 | 3-10 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Canvas, Goals, Constraints, Quality Attributes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CanvasArchitectureAlignmentWorkshop | JourneyCustomerService designCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
