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 Surveys |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 15-45 min | 3-14 Tage | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 | 50+ | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Survey Results, Charts, Segment Insights | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QuantitativeResearchValidation | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders |