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 Gemba Walk |  Operations Kaizen Event |  Operations PDCA Cycle |
|---|---|---|---|---|
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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 30-120 min | 0.5-5 Tage | 1 h bis mehrere Wochen |
Participantsdifferent | 1-4 | 2-6 | 4-10 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Observation Notes, Improvement Ideas | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | PDCA Log, Experiment Plan, Learning Outcome, Standard Change |
Tagsno overlap | ValidationDemandMVP | LeanObservationProcessOperations | LeanContinuous improvementOperations | Continuous improvementLeanExperiments |