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 Theory of Constraints |  Operations After-Action Review |  Operations Learning Review |
|---|---|---|---|---|
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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | High | High | Low | Medium |
Timedifferent | 0.5-2 Tage | 2-4 h Analyse, laufend | 20-45 min | 1-3 h |
Participantsdifferent | 6-12 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary | Learning Review Notes, System Factors, Improvement Actions |
Tags1 shared | Service designOperationsJourneyBlueprint | OperationsConstraintsFlowImprovement | LearningOperationsImprovement | LearningRetrospectiveIncidentOperations |