View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Operations PDCA Cycle | ![]() Growth A/B Testing | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | 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 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 | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 1 h bis mehrere Wochen | 1-4 Wochen | 1-5 Tage |
Participantsdifferent | 4-10 | 1-8 | 1-6 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Experiment results, Decision log, Learning summary | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | LeanFlowWasteDelivery | Continuous improvementLeanExperiments | ExperimentsGrowthAnalyticsValidation | ValidationExperimentsDemandDiscovery |



