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 Architecture Decision Record |  Operations A3 Problem Solving |  UX Design Service Blueprinting |  UX Research Customer Journey Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 15-45 min | 45-90 min | 0.5-2 Tage | 2-4 h |
Participantsdifferent | 1-3 | 2-5 | 6-12 | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | A3 Report, Action Plan, Root Cause Analysis | Service Blueprint, Fail Points, Ownership Map | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanProblem solvingCoachingOperations | Service designOperationsJourneyBlueprint | JourneyServiceService design |