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 paper-based illustration representing Pirate Metrics (AARRR) with its core stages and visible working result.
Growth
Pirate Metrics AARRR
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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
For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks.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.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
MediumLowMediumHigh
Timedifferent
1-2 h Setup, laufend45-90 min15-60 min je Zyklus1-4 Wochen
Participantsdifferent
2-83-121-81-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
AARRR funnel, Metric baseline, Experiment backlogForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action UpdatesExperiment results, Decision log, Learning summary
Tagsno overlap
GrowthMetricsExperiments
ChangeDecisionStrategy
DecisionChangeLearningStrategy
ExperimentsGrowthAnalyticsValidation
Add more methods