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 | ![]() Decision Making Argument Mapping | ![]() Innovation TRIZ | ![]() Decision Making DACI |
|---|---|---|---|---|
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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-4 h | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 2-8 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale | Contradiction Statement, Inventive Principles, Solution Concepts | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale | InnovationProblem solvingContradictionsCreativity | DecisionRolesGovernanceAlignment |



