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 ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |  Product Discovery Smoke Test |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min | 1-5 Tage |
Participantsdifferent | 1-4 | Designers, developers as users, and facilitation | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking | Interest Metrics, Conversion Signal, Learning Note |
Tags1 shared | ValidationDemandMVP | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandGrowth |