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 MORT Analysis |  Innovation Lean Startup |  Operations Family Tree Analysis |
|---|---|---|---|---|
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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | Mehrere Tage bis Wochen | Wochen bis Monate je Lernzyklus | 2-4 h |
Participantsdifferent | 1-4 | 2-6 | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ValidationDemandMVP | Root causeSafetySystemicIncident | LeanStartupValidationMVP | Root causePatternsIncidentSystemic |