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 Responsibility Poker |  Facilitation Expectation 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 | Half day initial, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Responsibility Map, Role Agreements, Open Questions | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCommunicationService | RolesResponsibilityTeamFacilitation | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
