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 |  Facilitation Alignment Mapping |  Product Strategy KPI Tree |  Engineering Goal Question Metric |
|---|---|---|---|---|
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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-2 h | 90-180 min initial, dann laufend | 90-180 min |
Participantsdifferent | 1-4 | 4-12 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Alignment Map, Open Issues, Decision Questions | KPI Tree, Owner List | GQM Table, Metric Profiles |
Tagsno overlap | ValidationDemandMVP | AlignmentStakeholdersStrategyFacilitation | MetricsStrategyAlignmentMeasurement | MetricsMeasurementEngineeringAlignment |