View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Growth Funnel Analysis |  Product Discovery Assumption Mapping |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 45-60 min | 15-30 min |
Participantsdifferent | 2-5 | 1-5 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Funnel report, Drop-off analysis, Optimization hypotheses | Assumption map, Test backlog, Risk ranking | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | AnalyticsConversionGrowth | AssumptionsRiskExperimentsValidation | Root causeIncidentLeanProblem solving |