View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Double Diamond | ![]() Agile Sprint Retrospective | ![]() Agile Sailboat Retrospective | ![]() Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | 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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 | Low |
Timedifferent | Wochen bis Monate | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 20-45 min |
Participantsdifferent | 3-12 | Scrum Team | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Improvement actions, Team agreements | Sailboat Board, Risks, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessDivergenceInnovation | RetrospectiveImprovementLearning | RetrospectiveTeamImprovement | LearningOperationsImprovement |



