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 Root Cause Analysis |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Low | High | Medium | High |
Timedifferent | Stunden bis wenige Tage | 2-6 h | 1-4 h | 2-8 h |
Participantsdifferent | 1-4 | 3-10 | 3-8 | 2-8 |
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 | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ValidationDemandMVP | RiskQualityOperationsRoot cause | Root causeProblem solvingQualityIncident | Problem solvingRoot causeDecisionOperations |