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 Strategy Lean Canvas |  Agile Sprint Retrospective |  Operations A3 Problem Solving |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. | 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 | Low | Medium | Low |
Timedifferent | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 15-30 min |
Participantsdifferent | 1-6 | Scrum Team | 2-5 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Lean Canvas, Core Assumptions, Experiment Backlog | Improvement actions, Team agreements | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures |
Tagsno overlap | StartupLeanAssumptionsBusiness model | RetrospectiveImprovementLearning | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving |