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 Research Customer Journey Mapping |  Operations Theory of Constraints |  Operations After-Action Review |  Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 | Medium | High | Low | Medium |
Timedifferent | 2-4 h | 2-4 h Analyse, laufend | 20-45 min | 1-3 h |
Participantsdifferent | 4-10 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | JourneyServiceService design | OperationsConstraintsFlowImprovement | LearningOperationsImprovement | LearningRetrospectiveIncidentOperations |