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 User Interviews |  Architecture arc42 |  Decision Making Trade-off Analysis |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. | 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 | Low | Low | Medium | Low |
Timedifferent | 30–60 min per interview | 1-2 Tage | 45-120 min | 15-45 min |
Participantsdifferent | 1 participant per interview | 1-4 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Architecture Document, Context View, Runtime View, Deployment View | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides | ADR File, Decision Log, Rationale |
Tagsno overlap | QualitativeResearchCustomerDiscovery | ArchitectureDocumentationCommunication | TradeoffsDecisionCriteriaOptions | ArchitectureRationaleDocumentationGovernance |