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 PDCA Cycle.
Operations
PDCA Cycle
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Purposedifferent
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.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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1 h bis mehrere Wochen1-4 Wochen1-3 h1-5 Tage
Participantsdifferent
1-81-64-10Nutzertraffic
Formatdifferent
Workshop + asyncAsyncWorkshopAsync
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeExperiment results, Decision log, Learning summaryCurrent-state map, Future-state map, Bottleneck listClick Data, Interest Signal, Learning Decision
Tagsno overlap
Continuous improvementLeanExperiments
ExperimentsGrowthAnalyticsValidation
LeanFlowWasteDelivery
ValidationExperimentsDemandDiscovery
Add more methods