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 After-Action Review |
|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 1-6 | Scrum Team | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lean Canvas, Core Assumptions, Experiment Backlog | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tagsno overlap | StartupLeanAssumptionsBusiness model | RetrospectiveImprovementLearning | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
