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
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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 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.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.
Complexitydifferent
LowHighLowLow
Timedifferent
30-60 min1-4 Wochen30-60 min45-90 min
Participantsdifferent
3-121-63-104-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsExperiment results, Decision log, Learning summaryEmotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
ExperimentsGrowthAnalyticsValidation
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
Add more methods