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 Architecture Decision Record |  UX Research User Interviews |  Architecture Request for Comments |  Decision Making DACI |
|---|---|---|---|---|
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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 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 | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30–60 min per interview | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 1-3 | 1 participant per interview | 3-20 Reviewer | 2-10 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Themes, Insight Summary | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualitativeResearchCustomerDiscovery | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment |