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 Research Customer Journey Mapping |  Architecture Architecture Decision Record |  Architecture Views and Beyond |
|---|---|---|---|---|
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 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. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 2-4 h | 15-45 min | 1-3 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-10 | 1-3 | 1-4 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Journey Map, Pain-point List, Opportunity Backlog | ADR File, Decision Log, Rationale | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | JourneyServiceService design | ArchitectureRationaleDocumentationGovernance | DocumentationStakeholdersArchitecture |