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 |  UX Design Customer Journey Canvas |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 45-90 min | 1-3 h | 60-120 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Team API Document | Expectation Map, Alignment Notes, Agreements | Customer Journey Canvas, Pain Points, Experience Opportunities | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TeamAlignmentCommunicationService | AlignmentStakeholdersTeam | JourneyCustomerService designCanvas | ArchitectureCommunicationStakeholdersCanvas |