View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Contradiction Analysis | ![]() Decision Making DACI | ![]() Architecture Architecture Decision Record | ![]() Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 60-120 min | 30-60 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 2-10 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | DACI Matrix, Decision Owner, Decision Log | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ContradictionsInnovationProblem solving | DecisionRolesGovernanceAlignment | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |



