View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Affinity DiagrammingArchitecture Decision RecordRequest for CommentsDecision Rights Mapping
| Criterion |  UX Research Affinity Diagramming |  Architecture Architecture Decision Record |  Architecture Request for Comments |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45–90 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 3-10 | 1-3 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |