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 Process Mapping |  Operations Theory of Constraints |  Agile Sprint Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Medium | High | Low | Low |
Timedifferent | 1-3 h | 2-4 h Analyse, laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 3-10 | 3-12 | Scrum Team | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Constraint Map, Improvement Plan, Flow Metrics | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tags1 shared | ProcessOperationsImprovement | OperationsConstraintsFlowImprovement | RetrospectiveImprovementLearning | LearningOperationsImprovement |