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 TRIZ |
|---|---|---|---|
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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 1-4 h |
Participantsdifferent | 3-20 Reviewer | 1-3 | 2-8 |
Formatdifferent | Async | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Contradiction Statement, Inventive Principles, Solution Concepts |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | InnovationProblem solvingContradictionsCreativity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
