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:HEART Framework ARID (Active Reviews for Intermediate Designs)A/B Testing Pirate Metrics AARRR

Criterion	UX Research HEART Framework	Architecture ARID (Active Reviews for Intermediate Designs)	Growth A/B Testing	Growth Pirate Metrics AARRR
Purposedifferent	Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.	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.	For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks.
Complexitydifferent	Medium	Medium	High	Medium
Timedifferent	120 min initial, dann laufend	2–4 h review as a planning range; preparation and evaluation additional	1-4 Wochen	1-2 h Setup, laufend
Participantsdifferent	3-6	Designers, developers as users, and facilitation	1-6	2-8
Formatdifferent	Workshop + async	Workshop + async	Async	Workshop + async
Outputdifferent	HEART-GSM Table, Dashboard	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Experiment results, Decision log, Learning summary	AARRR funnel, Metric baseline, Experiment backlog
Tagsno overlap	MetricsUX researchMeasurementSatisfaction	ArchitectureEngineeringFeedbackValidationTasks	ExperimentsGrowthAnalyticsValidation	GrowthMetricsExperiments

Add more methods