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
Growth Experiment workspace showing the question, observations, and next decision.
Growth
Growth Experiment
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
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.When growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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 h1-2 Wochen1 h bis mehrere Wochen1-4 Wochen
Participantsdifferent
4-101-61-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Current-state map, Future-state map, Bottleneck listExperiment card, Result summary, Next betPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeExperiment results, Decision log, Learning summary
Tagsno overlap
LeanFlowWasteDelivery
MarketingGrowthExperimentsLearning
Continuous improvementLeanExperiments
ExperimentsGrowthAnalyticsValidation
Add more methods