View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations PDCA Cycle |  Product Discovery Pretotyping |  Product Discovery Assumption Mapping |  Innovation Lean Startup |
|---|---|---|---|---|
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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1 h bis mehrere Wochen | Stunden bis wenige Tage | 45-60 min | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-8 | 1-4 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | Continuous improvementLeanExperiments | ValidationDemandMVP | AssumptionsRiskExperimentsValidation | LeanStartupValidationMVP |