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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration for OODA Loop.
Decision Making
OODA Loop
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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.
Complexitydifferent
LowLowMediumHigh
Timedifferent
45-90 min1-5 Tage15-60 min je Zyklus1-4 Wochen
Participantsdifferent
3-12Nutzertraffic1-81-6
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesInterest Metrics, Conversion Signal, Learning NoteSituation Assessment, Decision Loop, Action UpdatesExperiment results, Decision log, Learning summary
Tagsno overlap
ChangeDecisionStrategy
ValidationExperimentsDemandGrowth
DecisionChangeLearningStrategy
ExperimentsGrowthAnalyticsValidation
Add more methods