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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.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
LowMediumLowHigh
Timedifferent
20-60 min1-3 h20-35 min1-4 Wochen
Participantsdifferent
1-41-51-51-6
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathFunnel report, Drop-off analysis, Optimization hypothesesTest Card with a pre-set thresholdExperiment results, Decision log, Learning summary
Tagsno overlap
OperationsReliabilityDocumentation
AnalyticsConversionGrowth
ExperimentsValidationDiscoveryHypothesis
ExperimentsGrowthAnalyticsValidation
Add more methods