View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Goal Question Metric |  Product Discovery Riskiest Assumption Test |  Product Discovery Fake Door Test |  Product Strategy KPI Tree |
|---|---|---|---|---|
Purposedifferent | 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. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | 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. | When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 90-180 min | 1-2 Wochen pro Iteration | 1-5 Tage | 90-180 min initial, dann laufend |
Participantsdifferent | 3-6 | 2-6 | Nutzertraffic | 3-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | GQM Table, Metric Profiles | Prioritized Assumption List, Test Plan, Results Report | Click Data, Interest Signal, Learning Decision | KPI Tree, Owner List |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | ExperimentsValidationDiscoveryAssumptions | ValidationExperimentsDemandDiscovery | MetricsStrategyAlignmentMeasurement |