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 |  Operations After-Action Review |  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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 20-45 min | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 3-12 | 1-3 |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Lessons learned, Action items, Event summary | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | LearningOperationsImprovement | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
