View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Pretotyping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Lean Startup |
|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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 uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Low | High | Medium |
Timedifferent | Stunden bis wenige Tage | Several meetings plus preparation and analysis; total effort depends on scope | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ValidationDemandMVP | ArchitectureQualityRiskTradeoffsStakeholders | LeanStartupValidationMVP |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
