View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogCustomer Journey CanvasArchitecture Decision RecordArchitecture Communication Canvas
| Criterion |  Delivery RAID Log |  UX Design Customer Journey Canvas |  Architecture Architecture Decision Record |  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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | 15-45 min | 60-120 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 1-3 | 2-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |