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
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
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.When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.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.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 Wochen30-60 min120 min initial, dann laufend1-5 Tage
Participantsdifferent
1-62-63-6Nutzertraffic
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Experiment results, Decision log, Learning summaryCounter Metric List, Guardrail DefinitionsHEART-GSM Table, DashboardInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
MetricsMeasurementStrategyExperiments
MetricsUX researchMeasurementSatisfaction
ValidationExperimentsDemandGrowth
Add more methods