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 |  Business Strategy Value Chain Analysis |  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. | 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 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 | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Half day | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 3-8 | 1-3 |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Value Chain Map, Lever List | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | StrategyBusiness modelDiagnosisAnalysis | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
