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 | ![]() UX Research Affinity Diagramming | ![]() 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. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 45–90 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 3-10 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale | Theme clusters, Insight statements, Opportunity areas | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale | SynthesisQualitativeRoot cause | DecisionRolesGovernanceAlignment |



