View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sprint Retrospective |  Growth Growth Experiment |  Operations After-Action Review |
|---|---|---|---|
Purposedifferent | 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. | When growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment. | 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 | Low | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-2 Wochen | 20-45 min |
Participantsdifferent | Scrum Team | 1-6 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Experiment card, Result summary, Next bet | Lessons learned, Action items, Event summary |
Tags1 shared | RetrospectiveImprovementLearning | MarketingGrowthExperimentsLearning | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
