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 Theory of Constraints | ![]() UX Design Service Blueprinting | ![]() Operations After-Action Review |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | High | Low |
Timedifferent | 2-4 h Analyse, laufend | 0.5-2 Tage | 20-45 min |
Participantsdifferent | 3-12 | 6-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Service Blueprint, Fail Points, Ownership Map | Lessons learned, Action items, Event summary |
Tags1 shared | OperationsConstraintsFlowImprovement | Service designOperationsJourneyBlueprint | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






