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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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
LowLowLowHigh
Timedifferent
30 min Setup, dann laufend1-5 Tage20-35 min1-4 Wochen
Participantsdifferent
1-3 maintaining, briefing for everyoneNutzertraffic1-51-6
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
RAID Log, Status Report SourceInterest Metrics, Conversion Signal, Learning NoteTest Card with a pre-set thresholdExperiment results, Decision log, Learning summary
Tagsno overlap
RiskTrackingStakeholdersGovernance
ValidationExperimentsDemandGrowth
ExperimentsValidationDiscoveryHypothesis
ExperimentsGrowthAnalyticsValidation
Add more methods