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 | ![]() Innovation Contradiction Analysis |
|---|---|---|---|
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. | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 60-120 min |
Participantsdifferent | 3-20 Reviewer | 1-3 | 2-8 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | ContradictionsInnovationProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






