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 VRIO Framework |  Architecture Architecture Decision Record |  Decision Making Argument Mapping |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 15-45 min | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 3-6 | 1-3 | 1-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | VRIO Table, Strategic Actions | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | StrategyDiagnosisBusiness modelCapability | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale |