View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  UX Research Customer Journey Mapping |  UX Design Service Blueprinting |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Low | Medium | High | Low |
Timedifferent | 1-2 Tage | 2-4 h | 0.5-2 Tage | 15-45 min |
Participantsdifferent | 1-4 | 4-10 | 6-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Journey Map, Pain-point List, Opportunity Backlog | Service Blueprint, Fail Points, Ownership Map | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | JourneyServiceService design | Service designOperationsJourneyBlueprint | ArchitectureRationaleDocumentationGovernance |