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 Sailboat Retrospective |  Operations Process Mapping |  Operations A3 Problem Solving |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 45-90 min | 45–75 min |
Participantsdifferent | 4-12 | 3-10 | 2-5 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Process Map, Handoff List, Improvement Backlog | A3 Report, Action Plan, Root Cause Analysis | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | ProcessOperationsImprovement | LeanProblem solvingCoachingOperations | RetrospectiveLearningReflectionTeam |