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 Architecture Decision Record |  Architecture Request for Comments |  Innovation Design Charrette |
|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | Halber Tag bis mehrere Tage |
Participantsdifferent | 1-3 | 3-20 Reviewer | 10-50 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | BrainstormingWorkshopCollaborationIdeation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
