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 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
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
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 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.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitydifferent
HighLowLowLow
Timedifferent
1-4 Wochen30-60 min1-5 Tage45-90 min
Participantsdifferent
1-63-12Nutzertraffic4-12
Formatdifferent
AsyncWorkshopAsyncWorkshop
Outputdifferent
Experiment results, Decision log, Learning summaryStart Stop Continue Board, Improvement ActionsInterest Metrics, Conversion Signal, Learning NoteStarfish Board, Practice Changes, Experiments
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
RetrospectiveImprovementTeamReflection
ValidationExperimentsDemandGrowth
RetrospectiveImprovementExperimentsTeam
Add more methods