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 Strategy Lean Canvas |  Engineering Hypothesis-Driven Troubleshooting |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 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 | Medium | Medium | High | Medium |
Timedifferent | 45-90 min | 30-240 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 1-6 | 1-6 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Lean Canvas, Core Assumptions, Experiment Backlog | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | StartupLeanAssumptionsBusiness model | TroubleshootingProblem solvingDiagnosis | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |