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 Starfish Retrospective |  Systems Thinking CATWOE Analysis |  Agile Sailboat Retrospective |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Medium | Low | Low |
Timesame | 45-90 min | 45-90 min | 45-90 min | 45-90 min |
Participantsdifferent | 4-12 | 3-8 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Sailboat Board, Risks, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | Systems thinkingFramingStakeholders | RetrospectiveTeamImprovement | AlignmentStakeholdersTeam |