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 Change Analysis |  Operations Kepner-Tregoe |  Operations A3 Problem Solving |
|---|---|---|---|---|
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 deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | Stunden bis wenige Tage | 45-120 min | 2-8 h | 45-90 min |
Participantsdifferent | 1-4 | 2-6 | 2-8 | 2-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Problem Analysis, Decision Analysis, Risk Plan | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ValidationDemandMVP | ChangeRoot causeTroubleshootingComparison | Problem solvingRoot causeDecisionOperations | LeanProblem solvingCoachingOperations |