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 DiagrammingARID (Active Reviews for Intermediate Designs)Request for CommentsDecision Rights Mapping
| Criterion | ![]() UX Research Affinity Diagramming | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | Medium | Medium | Medium |
Timedifferent | 45–90 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 3-10 | Designers, developers as users, and facilitation | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |



