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 | ![]() Innovation Lean Startup | ![]() Operations Causal Factor 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 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. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | 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 | Wochen bis Monate je Lernzyklus | 2-6 h | 15-30 min |
Participantsdifferent | 1-4 | 2-8 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Root cause notes, Countermeasures |
Tagsno overlap | ValidationDemandMVP | LeanStartupValidationMVP | CausalityIncidentRoot causeTimeline | Root causeIncidentLeanProblem solving |



