View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Surveys | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Decision Making DACI | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 3-14 Tage | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | 15-45 min |
Participantsdifferent | 50+ | Designers, developers as users, and facilitation | 2-10 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | Survey Results, Charts, Segment Insights | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | DACI Matrix, Decision Owner, Decision Log | ADR File, Decision Log, Rationale |
Tagsno overlap | QuantitativeResearchValidation | ArchitectureEngineeringFeedbackValidationTasks | DecisionRolesGovernanceAlignment | ArchitectureRationaleDocumentationGovernance |



