View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Agile Sailboat Retrospective |  Operations Process Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 2-5 | 4-12 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Sailboat Board, Risks, Improvement Actions | Process Map, Handoff List, Improvement Backlog | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | LeanProblem solvingCoachingOperations | RetrospectiveTeamImprovement | ProcessOperationsImprovement | RetrospectiveImprovementExperimentsTeam |