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

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	UX Research HEART Framework	Growth Pirate Metrics AARRR	Growth A/B Testing
Purposedifferent	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.	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.	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.	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	2–4 h review as a planning range; preparation and evaluation additional	120 min initial, dann laufend	1-2 h Setup, laufend	1-4 Wochen
Participantsdifferent	Designers, developers as users, and facilitation	3-6	2-8	1-6
Formatdifferent	Workshop + async	Workshop + async	Workshop + async	Async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	HEART-GSM Table, Dashboard	AARRR funnel, Metric baseline, Experiment backlog	Experiment results, Decision log, Learning summary
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	MetricsUX researchMeasurementSatisfaction	GrowthMetricsExperiments	ExperimentsGrowthAnalyticsValidation

Add more methods