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 for Flywheel.
Growth
Flywheel
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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
LowMediumLowHigh
Timedifferent
45-90 min60-120 min1-5 Tage1-4 Wochen
Participantsdifferent
3-123-8Nutzertraffic1-6
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesFlywheel Map, Friction Points, Growth Levers, Experiment BacklogInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
ChangeDecisionStrategy
GrowthRetentionConversion
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods