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 |  Operations Root Cause Tree Analysis |  UX Research Affinity Diagramming |
|---|---|---|---|---|
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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30–60 min per interview | 1-3 h | 45–90 min |
Participantsdifferent | 1-3 | 1 participant per interview | 2-8 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Themes, Insight Summary | Cause Tree, Evidence Notes, Countermeasures | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualitativeResearchCustomerDiscovery | Root causeTreeIncidentQuality | SynthesisQualitativeRoot cause |