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 for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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 Wochen45-90 min30-60 min1-5 Tage
Participantsdifferent
1-64-123-12Nutzertraffic
Formatdifferent
AsyncWorkshopWorkshopAsync
Outputdifferent
Experiment results, Decision log, Learning summarySailboat Board, Risks, Improvement ActionsStart Stop Continue Board, Improvement ActionsInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
RetrospectiveTeamImprovement
RetrospectiveImprovementTeamReflection
ValidationExperimentsDemandGrowth
Add more methods