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 Assumption Mapping |  Growth A/B Testing |  Growth North Star Metric |
|---|---|---|---|---|
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | When product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 90-180 min | 45-60 min | 1-4 Wochen | 1-2 h |
Participantsdifferent | 3-6 | 2-8 | 1-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | GQM Table, Metric Profiles | Assumption map, Test backlog, Risk ranking | Experiment results, Decision log, Learning summary | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | AssumptionsRiskExperimentsValidation | ExperimentsGrowthAnalyticsValidation | GrowthMetricsAlignmentRetention |