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 Team Charter |  UX Design Service Blueprinting |  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 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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | Low | Medium | High | Low |
Timedifferent | Half day initial, dann laufend | 2-4 h | 0.5-2 Tage | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 6-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Team Charter, Working Norms, Role Notes | Service Blueprint, Fail Points, Ownership Map | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCommunicationService | TeamAlignmentCollaboration | Service designOperationsJourneyBlueprint | AlignmentStakeholdersTeam |