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/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.
Complexitydifferent
HighLowLowMedium
Timedifferent
1-4 Wochen45-90 min30-60 min15-60 min je Zyklus
Participantsdifferent
1-63-122-61-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryForce Field Map, Change Levers, Risk NotesCounter Metric List, Guardrail DefinitionsSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
ChangeDecisionStrategy
MetricsMeasurementStrategyExperiments
DecisionChangeLearningStrategy
Add more methods