View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Pretotyping |  Operations Kaizen Event |  Operations PDCA Cycle |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. | 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 | Low | Medium | Low | High |
Timedifferent | Stunden bis wenige Tage | 0.5-5 Tage | 1 h bis mehrere Wochen | 1-4 Wochen |
Participantsdifferent | 1-4 | 4-10 | 1-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationDemandMVP | LeanContinuous improvementOperations | Continuous improvementLeanExperiments | ExperimentsGrowthAnalyticsValidation |