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 ATAM (Architecture Tradeoff Analysis Method) |  Operations DMAIC |  Product Discovery Fake Door Test |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together. | 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 | High | High | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-12 Wochen | 1-5 Tage | 45-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + 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 | Project Charter, Measurement Plan, Cause Analysis, Control Plan | Click Data, Interest Signal, Learning Decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Continuous improvementQualityProcess improvement | ValidationExperimentsDemandDiscovery | AssumptionsRiskExperimentsValidation |