View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Growth A/B Testing |  Engineering Goal Question Metric |  Growth North Star Metric |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | 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 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 | High | Medium | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 90-180 min | 1-2 h |
Participantsdifferent | 2-8 | 1-6 | 3-6 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Experiment results, Decision log, Learning summary | GQM Table, Metric Profiles | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ExperimentsGrowthAnalyticsValidation | MetricsMeasurementEngineeringAlignment | GrowthMetricsAlignmentRetention |