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 |  Product Discovery Fake Door Test |  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. | 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. | 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 | 1-5 Tage | 2-4 h |
Participantsdifferent | 1-4 | 2-6 | Nutzertraffic | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Click Data, Interest Signal, Learning Decision | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ValidationDemandMVP | Root causeSafetySystemicIncident | ValidationExperimentsDemandDiscovery | Root causePatternsIncidentSystemic |