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 User Story Mapping |  Operations A3 Problem Solving |  Decision Making Constraint Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut. | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 30-90 min | 15-30 min |
Participantsdifferent | 4-10 | 2-5 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Story Map, Release Slices, Backlog Candidates | A3 Report, Action Plan, Root Cause Analysis | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Root cause notes, Countermeasures |
Tagsno overlap | BacklogJourneyPlanningMVP | LeanProblem solvingCoachingOperations | ConstraintsDecisionPlanningOptions | Root causeIncidentLeanProblem solving |