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 Communication Plan |  Architecture arc42 |  Architecture Views and Beyond |
|---|---|---|---|---|
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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | High | Low | Low | Medium |
Timedifferent | 0.5-2 Tage | 45-90 min | 1-2 Tage | 1-3 Tage |
Participantsdifferent | 6-12 | 2-6 | 1-4 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Communication Plan, Channel Matrix, Message Cadence | Architecture Document, Context View, Runtime View, Deployment View | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | Service designOperationsJourneyBlueprint | CommunicationStakeholdersDeliveryPlanning | ArchitectureDocumentationCommunication | DocumentationStakeholdersArchitecture |