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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Flywheel.
Growth
Flywheel
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowMediumLowMedium
Timedifferent
20-60 min60-120 min1-5 Tage45-60 min
Participantsdifferent
1-43-8Nutzertraffic2-8
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathFlywheel Map, Friction Points, Growth Levers, Experiment BacklogInterest Metrics, Conversion Signal, Learning NoteAssumption map, Test backlog, Risk ranking
Tagsno overlap
OperationsReliabilityDocumentation
GrowthRetentionConversion
ValidationExperimentsDemandGrowth
AssumptionsRiskExperimentsValidation
Add more methods