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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Sailboat Board, Risks, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCollaboration | RetrospectiveTeamImprovement | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






