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

Criterion	Architecture Architecture Decision Record	Growth A/B Testing	Growth Pirate Metrics AARRR	Architecture ARID (Active Reviews for Intermediate Designs)
Purposedifferent	An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.	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.	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.
Complexitydifferent	Low	High	Medium	Medium
Timedifferent	15-45 min	1-4 Wochen	1-2 h Setup, laufend	2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent	1-3	1-6	2-8	Designers, developers as users, and facilitation
Formatdifferent	Async	Async	Workshop + async	Workshop + async
Outputdifferent	ADR File, Decision Log, Rationale	Experiment results, Decision log, Learning summary	AARRR funnel, Metric baseline, Experiment backlog	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap	ArchitectureRationaleDocumentationGovernance	ExperimentsGrowthAnalyticsValidation	GrowthMetricsExperiments	ArchitectureEngineeringFeedbackValidationTasks

Add more methods