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 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
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
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 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.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
1-4 Wochen90-180 min initial, dann laufend45-90 min30-60 min
Participantsdifferent
1-63-83-122-6
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryKPI Tree, Owner ListForce Field Map, Change Levers, Risk NotesCounter Metric List, Guardrail Definitions
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
MetricsStrategyAlignmentMeasurement
ChangeDecisionStrategy
MetricsMeasurementStrategyExperiments
Add more methods