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 |  Engineering Goal Question Metric |  UX Research HEART Framework |  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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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 | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 90-180 min | 120 min initial, dann laufend | 1-5 Tage |
Participantsdifferent | 1-4 | 3-6 | 3-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | GQM Table, Metric Profiles | HEART-GSM Table, Dashboard | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | MetricsMeasurementEngineeringAlignment | MetricsUX researchMeasurementSatisfaction | ValidationExperimentsDemandDiscovery |