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 Start Stop Continue | ![]() Agile Sailboat Retrospective | ![]() Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 30-60 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






