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 |  Decision Making OODA Loop |  Domain Modeling Context Map |  UX Design Customer Journey Canvas |
|---|---|---|---|---|
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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 0.5-2 Tage | 15-60 min je Zyklus | 1-3 h | 1-3 h |
Participantsdifferent | 6-12 | 1-8 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Situation Assessment, Decision Loop, Action Updates | Context Map, Integration Patterns, Boundary Notes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | Service designOperationsJourneyBlueprint | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesStrategy | JourneyCustomerService designCanvas |