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 Architecture Decision Record |  Innovation TRIZ |  Decision Making RAPID |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 15-45 min | 1-4 h | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 2-8 | 3-12 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Contradiction Statement, Inventive Principles, Solution Concepts | RAPID Role Map, Recommendation, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | InnovationProblem solvingContradictionsCreativity | DecisionRolesGovernance | ArchitectureDecisionAsyncGovernance |