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) |  Product Discovery Concierge MVP |  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. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen | 45-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 Kunden | 2-8 |
Formatsame | Workshop + async | Workshop + 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 | Concierge Learnings, Service Blueprint, MVP Risks | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | MVPValidationServiceDiscovery | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
