methodatlas
Compare

View methods side by side.

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

Criterion
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A paper-based illustration representing Pirate Metrics (AARRR) with its core stages and visible working result.
Growth
Pirate Metrics AARRR
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
HighLowMediumLow
Timedifferent
1-4 Wochen1-2 Tage1-2 h Setup, laufend1-5 Tage
Participantsdifferent
1-61-42-8Nutzertraffic
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Experiment results, Decision log, Learning summaryArchitecture Document, Context View, Runtime View, Deployment ViewAARRR funnel, Metric baseline, Experiment backlogInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
ArchitectureDocumentationCommunication
GrowthMetricsExperiments
ValidationExperimentsDemandGrowth
Add more methods