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 | ![]() Operations A3 Problem Solving | ![]() 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. | 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. | 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 | Low |
Timedifferent | 0.5-2 Tage | 45-90 min | 15-45 min |
Participantsdifferent | 6-12 | 2-5 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | A3 Report, Action Plan, Root Cause Analysis | ADR File, Decision Log, Rationale |
Tagsno overlap | Service designOperationsJourneyBlueprint | LeanProblem solvingCoachingOperations | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






