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 |  UX Design Customer Journey Canvas |  Architecture C4 Model |  Architecture Architecture Inception 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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-4 h | 1-2 h |
Participantsdifferent | 3-20 Reviewer | 3-10 | 1-5 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Customer Journey Canvas, Pain Points, Experience Opportunities | Context Diagram, Container Diagram, Component Diagram | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | JourneyCustomerService designCanvas | ArchitectureCommunicationVisualization | AlignmentArchitectureCanvas |