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 Architecture Decision Record | ![]() Engineering Golden Path | ![]() Product Discovery Fake Door 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When teams need a reliable default path for frequent use, sprawl quickly emerges without any guiding logic. Golden Path bundles the preferred path so good practice becomes easy and deviation becomes deliberate. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 15-45 min | 1-3 Tage Setup, laufend | 1-5 Tage |
Participantsdifferent | 1-4 | 1-3 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | ADR File, Decision Log, Rationale | Golden Path Guide, Templates, Quality Checks | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | ArchitectureRationaleDocumentationGovernance | EngineeringProductivityGovernance | ValidationExperimentsDemandDiscovery |



