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 |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | 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 | Low | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 30-120 min | 0.5-5 Tage | 1-5 Tage |
Participantsdifferent | 1-4 | 2-6 | 4-10 | Nutzertraffic |
Formatdifferent | Workshop + async | 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 | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | LeanObservationProcessOperations | LeanContinuous improvementOperations | ValidationExperimentsDemandDiscovery |