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 Failure Mode and Effects Analysis |  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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | High | High | Medium |
Timedifferent | Stunden bis wenige Tage | 2-6 h | 2-6 h | 2-4 h |
Participantsdifferent | 1-4 | 3-10 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | FMEA Table, Risk Priority, Mitigation Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ValidationDemandMVP | RiskQualityOperationsRoot cause | RiskRoot causeSafety | Root causeSafetyIncident |