View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Agile Start Stop Continue |  Facilitation Expectation Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 30-60 min | 45-90 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Start Stop Continue Board, Improvement Actions | Expectation Map, Alignment Notes, Agreements | Starfish Board, Practice Changes, Experiments |
Tags1 shared | TeamAlignmentCommunicationService | RetrospectiveImprovementTeamReflection | AlignmentStakeholdersTeam | RetrospectiveImprovementExperimentsTeam |