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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.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
HighMediumMediumLow
Timedifferent
1-4 Wochen15-60 min je Zyklus90-180 min initial, dann laufend45-90 min
Participantsdifferent
1-61-83-83-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Experiment results, Decision log, Learning summarySituation Assessment, Decision Loop, Action UpdatesKPI Tree, Owner ListForce Field Map, Change Levers, Risk Notes
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
DecisionChangeLearningStrategy
MetricsStrategyAlignmentMeasurement
ChangeDecisionStrategy
Add more methods