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
Growth Experiment workspace showing the question, observations, and next decision.
Growth
Growth Experiment
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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 growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
HighMediumLowLow
Timedifferent
1-4 Wochen1-2 Wochen45–75 min30-60 min
Participantsdifferent
1-61-6Team members involved3-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Experiment results, Decision log, Learning summaryExperiment card, Result summary, Next bet4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
MarketingGrowthExperimentsLearning
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods