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 for OODA Loop.
Decision Making
OODA Loop
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
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
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.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.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.
Complexitydifferent
MediumHighLowLow
Timedifferent
15-60 min je Zyklus1-4 Wochen30-60 min45-90 min
Participantsdifferent
1-81-62-63-12
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesExperiment results, Decision log, Learning summaryCounter Metric List, Guardrail DefinitionsForce Field Map, Change Levers, Risk Notes
Tagsno overlap
DecisionChangeLearningStrategy
ExperimentsGrowthAnalyticsValidation
MetricsMeasurementStrategyExperiments
ChangeDecisionStrategy
Add more methods