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 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Fake Door Test |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 1-5 Tage | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | Nutzertraffic | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | 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 | Click Data, Interest Signal, Learning Decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | ValidationExperimentsDemandDiscovery | AssumptionsRiskExperimentsValidation |