View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations A3 Problem Solving | ![]() Architecture Architecture Decision Record | ![]() UX Design Service Blueprinting |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 45-90 min | 15-45 min | 0.5-2 Tage |
Participantsdifferent | 2-5 | 1-3 | 6-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | ADR File, Decision Log, Rationale | Service Blueprint, Fail Points, Ownership Map |
Tagsno overlap | LeanProblem solvingCoachingOperations | ArchitectureRationaleDocumentationGovernance | Service designOperationsJourneyBlueprint |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






