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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
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 Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.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 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
Ongoing1-4 Wochen30-60 min45-90 min
Participantsdifferent
1-201-63-124-12
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Visual Board, Status Indicators, Exception CuesExperiment results, Decision log, Learning summaryStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
SignalsOperationsVisual management
ExperimentsGrowthAnalyticsValidation
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods