View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  UX Research Surveys |  Product Discovery Smoke Test |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | 30 min Setup, dann laufend | 3-14 Tage | 1-5 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 50+ | Nutzertraffic | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Survey Results, Charts, Segment Insights | Interest Metrics, Conversion Signal, Learning Note | 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 | RiskTrackingStakeholdersGovernance | QuantitativeResearchValidation | ValidationExperimentsDemandGrowth | ArchitectureQualityRiskTradeoffsStakeholders |