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 Bottleneck Analysis |  Operations 5 Whys |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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 flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | 0.5-2 Tage | 1-3 h | 15-30 min | 2-8 h |
Participantsdifferent | 6-12 | 3-8 | 2-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | Service designOperationsJourneyBlueprint | FlowMeasurementConstraints | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations |