Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:North Star Metric Goal Question Metric ARID (Active Reviews for Intermediate Designs)A/B Testing

Criterion	Growth North Star Metric	Engineering Goal Question Metric	Architecture ARID (Active Reviews for Intermediate Designs)	Growth A/B Testing
Purposedifferent	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.	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.	ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.	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.
Complexitydifferent	Medium	Medium	Medium	High
Timedifferent	1-2 h	90-180 min	2–4 h review as a planning range; preparation and evaluation additional	1-4 Wochen
Participantsdifferent	3-8	3-6	Designers, developers as users, and facilitation	1-6
Formatdifferent	Workshop + async	Workshop	Workshop + async	Async
Outputdifferent	North Star metric, Input metric tree, Measurement cadence	GQM Table, Metric Profiles	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Experiment results, Decision log, Learning summary
Tagsno overlap	GrowthMetricsAlignmentRetention	MetricsMeasurementEngineeringAlignment	ArchitectureEngineeringFeedbackValidationTasks	ExperimentsGrowthAnalyticsValidation

Add more methods