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 arc42 |  Innovation Design Charrette |  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. | 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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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 | Low | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage | Halber Tag bis mehrere Tage | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 1-4 | 10-50 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication | BrainstormingWorkshopCollaborationIdeation | ArchitectureRationaleDocumentationGovernance |