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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
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 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 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.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
45-90 min1-4 Wochen30-60 min90-180 min initial, dann laufend
Participantsdifferent
3-121-62-63-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesExperiment results, Decision log, Learning summaryCounter Metric List, Guardrail DefinitionsKPI Tree, Owner List
Tagsno overlap
ChangeDecisionStrategy
ExperimentsGrowthAnalyticsValidation
MetricsMeasurementStrategyExperiments
MetricsStrategyAlignmentMeasurement
Add more methods