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 Fishbone Diagram |  Operations Fault Tree Analysis |  Operations Barrier 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | Stunden bis wenige Tage | 30-60 min | 2-6 h | 2-4 h |
Participantsdifferent | 1-4 | 2-8 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Fishbone Diagram, Cause Categories, Investigation Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ValidationDemandMVP | Root causeQualityOperations | RiskRoot causeSafety | Root causeSafetyIncident |