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 | ![]() UX Research Affinity Diagramming | ![]() Decision Making Decision Rights Mapping | ![]() 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 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 organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | Low | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45–90 min | 90-180 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 4-12 | 2-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Theme clusters, Insight statements, Opportunity areas | Decision Rights Matrix, Agreement | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SynthesisQualitativeRoot cause | DecisionGovernanceAlignmentResponsibility | DecisionRolesGovernanceAlignment |



