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 Request for Comments |  Decision Making DACI |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
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 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 1-2 h |
Participantsdifferent | 3-10 | 3-20 Reviewer | 2-10 | 3-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | JourneyCustomerService designCanvas | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment | CanvasArchitectureAlignmentWorkshop |