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
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
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
When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.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
MediumMediumLowHigh
Timedifferent
1-3 h60-120 min1-5 Tage1-4 Wochen
Participantsdifferent
4-103-8Nutzertraffic1-6
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Current-state map, Future-state map, Bottleneck listFlywheel Map, Friction Points, Growth Levers, Experiment BacklogInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
LeanFlowWasteDelivery
GrowthRetentionConversion
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods