View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  UX Design Customer Journey Canvas |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 60-90 min | 60–90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 3-6 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Customer Journey Canvas, Pain Points, Experience Opportunities | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RiskTrackingStakeholdersGovernance | JourneyCustomerService designCanvas | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |