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 MVP Test Matrix with a method-specific labelled workspace.
Product Discovery
MVP Test Matrix
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan.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.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
HighMediumLowMedium
Timedifferent
1-4 Wochen45-75 min45-90 min15-60 min je Zyklus
Participantsdifferent
1-62-83-121-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryTest Matrix, Test PlanForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
ExperimentsValidationDiscoveryOptions
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods