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 of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
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.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.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 min20-35 min1-4 Wochen
Participantsdifferent
4-103-81-51-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Current-state map, Future-state map, Bottleneck listFlywheel Map, Friction Points, Growth Levers, Experiment BacklogTest Card with a pre-set thresholdExperiment results, Decision log, Learning summary
Tagsno overlap
LeanFlowWasteDelivery
GrowthRetentionConversion
ExperimentsValidationDiscoveryHypothesis
ExperimentsGrowthAnalyticsValidation
Add more methods