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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
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 Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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'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
MediumHighLowLow
Timedifferent
Ongoing1-4 Wochen30-60 min30-60 min
Participantsdifferent
2-201-63-123-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Chat Transcript, Action Log, AutomationsExperiment results, Decision log, Learning summaryStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
CollaborationEngineeringIncident
ExperimentsGrowthAnalyticsValidation
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods