View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)User InterviewsRAID LogArchitecture Decision Record
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Research User Interviews |  Delivery RAID Log |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | High | Low | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30–60 min per interview | 30 min Setup, dann laufend | 15-45 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1 participant per interview | 1-3 maintaining, briefing for everyone | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Interview Notes, Themes, Insight Summary | RAID Log, Status Report Source | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | QualitativeResearchCustomerDiscovery | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance |