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 Scrum with its method-specific working model.
Agile
Scrum
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Purposedifferent
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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 headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-4 Wochen je Sprint, laufendHalf day1-4 Wochen30-60 min
Participantsdifferent
3-10 (Scrum Team)3-121-62-6
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalLeverage Map, Action StrategyExperiment results, Decision log, Learning summaryCounter Metric List, Guardrail Definitions
Tagsno overlap
AgileIterationCadence
Systems thinkingChangeStrategy
ExperimentsGrowthAnalyticsValidation
MetricsMeasurementStrategyExperiments
Add more methods