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) |  Business Strategy 5-Minuten VC-Check |
|---|---|---|---|
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. | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. |
Complexitydifferent | Low | High | Low |
Timedifferent | Stunden bis wenige Tage | Several meetings plus preparation and analysis; total effort depends on scope | 5-15 min |
Participantsdifferent | 1-4 | Evaluation team, architects, and relevant stakeholders | 1-5 |
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 | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step |
Tagsno overlap | ValidationDemandMVP | ArchitectureQualityRiskTradeoffsStakeholders | StartupValidationCompetition |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
