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 Quality Attribute Workshop |  Decision Making Argument Mapping |  Architecture Request for Comments |
|---|---|---|---|---|
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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 2-4 h | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 5-15 | 1-8 | 3-20 Reviewer |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Quality Scenarios, Priority List, Architecture Concerns | Argument Map, Evidence Gaps, Decision Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RequirementsArchitectureWorkshop | SensemakingDecisionRationale | ArchitectureDecisionAsyncGovernance |