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 |  Facilitation Expectation Mapping |  Agile Starfish Retrospective |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 45-90 min | 45-90 min | 1-2 h |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Expectation Map, Alignment Notes, Agreements | Starfish Board, Practice Changes, Experiments | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TeamAlignmentCommunicationService | AlignmentStakeholdersTeam | RetrospectiveImprovementExperimentsTeam | AlignmentStakeholdersStrategyFacilitation |