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 |  Facilitation Storytelling |  Architecture Views and Beyond |  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. | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | 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. | 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 | Medium | Medium | Low |
Timedifferent | 0.5-2 Tage | 45-120 min | 1-3 Tage | 15-45 min |
Participantsdifferent | 6-12 | 1-6 | 1-4 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Narrative Outline, Key Message, Story Arc | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | Service designOperationsJourneyBlueprint | CommunicationNarrativeStakeholdersFacilitation | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |