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 for Flywheel.
Growth
Flywheel
Paper illustration for NoEstimates.
Agile
NoEstimates
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
MediumMediumHighLow
Timedifferent
60-120 minlaufend1-4 Wochen1-5 Tage
Participantsdifferent
3-82-121-6Nutzertraffic
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogThroughput Data, Flow Forecast, Slicing RulesExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
GrowthRetentionConversion
EstimationForecastingFlow
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods