View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordAffinity DiagrammingARID (Active Reviews for Intermediate Designs)
| Criterion |  Architecture Architecture Decision Record |  UX Research Affinity Diagramming |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 15-45 min | 45–90 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-3 | 3-10 | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Theme clusters, Insight statements, Opportunity areas | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeRoot cause | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
