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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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
HighLowLowLow
Timedifferent
1-4 Wochen30 min Setup, dann laufend20-40 min initial, dann laufend1-5 Tage
Participantsdifferent
1-61-3 maintaining, briefing for everyone3-15Nutzertraffic
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
Experiment results, Decision log, Learning summaryRAID Log, Status Report SourceROAM Board, Owner ListInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
ValidationExperimentsDemandGrowth
Add more methods