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 |  Business Strategy Value Chain Analysis |  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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 | High | Medium |
Timedifferent | 15-45 min | Half day | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 3-8 | 3-20 Reviewer |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Value Chain Map, Lever List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StrategyBusiness modelDiagnosisAnalysis | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
