View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Service Blueprinting | ![]() Delivery RAID Log | ![]() Architecture Architecture Communication Canvas | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 0.5-2 Tage | 30 min Setup, dann laufend | 60-120 min | 15-45 min |
Participantsdifferent | 6-12 | 1-3 maintaining, briefing for everyone | 2-8 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | Service designOperationsJourneyBlueprint | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance |



