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 Root Cause Tree Analysis |  Operations Failure Mode and Effects Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | Stunden bis wenige Tage | 1-3 h | 2-6 h | 15-30 min |
Participantsdifferent | 1-4 | 2-8 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Cause Tree, Evidence Notes, Countermeasures | FMEA Table, Risk Priority, Mitigation Actions | Root cause notes, Countermeasures |
Tagsno overlap | ValidationDemandMVP | Root causeTreeIncidentQuality | RiskQualityOperationsRoot cause | Root causeIncidentLeanProblem solving |