View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Agile Sailboat Retrospective |  Facilitation Expectation Mapping |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-12 | 4-12 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Sailboat Board, Risks, Improvement Actions | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions |
Tags1 shared | TeamAlignmentCollaboration | RetrospectiveTeamImprovement | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection |