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 |  Innovation Lean Startup |  Operations Fishbone Diagram |
|---|---|---|---|---|
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 uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 2-6 h | Wochen bis Monate je Lernzyklus | 30-60 min |
Participantsdifferent | 1-4 | 3-10 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | FMEA Table, Risk Priority, Mitigation Actions | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ValidationDemandMVP | RiskQualityOperationsRoot cause | LeanStartupValidationMVP | Root causeQualityOperations |