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 |  UX Research Customer Journey Mapping |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | Half day initial, dann laufend | 2-4 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 4-10 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Team API Document | Journey Map, Pain-point List, Opportunity Backlog | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | TeamAlignmentCommunicationService | JourneyServiceService design | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |