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 |  Agile ROAM Board |  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 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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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 | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 20-40 min initial, dann laufend | 60-120 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 3-15 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Customer Journey Canvas, Pain Points, Experience Opportunities | ROAM Board, Owner List | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | JourneyCustomerService designCanvas | RiskAgileTrackingAlignment | ArchitectureCommunicationStakeholdersCanvas |