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 of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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
LowLowLowHigh
Timedifferent
45-90 min30-60 min1-5 Tage1-4 Wochen
Participantsdifferent
3-122-6Nutzertraffic1-6
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesCounter Metric List, Guardrail DefinitionsInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
ChangeDecisionStrategy
MetricsMeasurementStrategyExperiments
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods