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 A3 Problem Solving |  Operations Kepner-Tregoe |  Agile Start Stop Continue |
|---|---|---|---|---|
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. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45-90 min | 45-90 min | 2-8 h | 30-60 min |
Participantsdifferent | 4-12 | 2-5 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | A3 Report, Action Plan, Root Cause Analysis | Problem Analysis, Decision Analysis, Risk Plan | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | LeanProblem solvingCoachingOperations | Problem solvingRoot causeDecisionOperations | RetrospectiveImprovementTeamReflection |