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 Service Blueprinting |  UX Design Customer Journey Canvas |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | High | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 0.5-2 Tage | 1-3 h | 60-120 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 6-12 | 3-10 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Service Blueprint, Fail Points, Ownership Map | Customer Journey Canvas, Pain Points, Experience Opportunities | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Service designOperationsJourneyBlueprint | JourneyCustomerService designCanvas | ArchitectureCommunicationStakeholdersCanvas |