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 Architecture Decision Record |  Business Strategy VRIO Framework |
|---|---|---|---|
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. | 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. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | 1-3 | 3-6 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | VRIO Table, Strategic Actions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | StrategyDiagnosisBusiness modelCapability |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
