View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Starfish RetrospectiveExpectation MappingTeam Topologies Interaction ModesSailboat Retrospective
| Criterion |  Agile Starfish Retrospective |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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. | 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. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | Half day | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | Team-Leads plus Architecture | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization | RetrospectiveTeamImprovement |