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 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 Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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'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
LowMediumHighLow
Timedifferent
45–75 min60-120 min1-4 Wochen30-60 min
Participantsdifferent
Team members involved3-81-63-10
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summaryEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
RetrospectiveTeamReflection
Add more methods