View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Customer Journey Mapping |  Facilitation Expectation Mapping |  Facilitation Stakeholder Salience Model |  Team Design Team API |
|---|---|---|---|---|
Purposedifferent | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 45-90 min | 60-90 min | Half day initial, dann laufend |
Participantsdifferent | 4-10 | 3-12 | 3-6 | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class | Team API Document |
Tagsno overlap | JourneyServiceService design | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance | TeamAlignmentCommunicationService |