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 Bottleneck Analysis | ![]() Agile 4Ls 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 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. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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 | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 h | 45–75 min | 20-45 min |
Participantsdifferent | 3-10 | 3-8 | Team members involved | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | 4Ls Board, Learning Themes, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | FlowMeasurementConstraints | RetrospectiveLearningReflectionTeam | LearningOperationsImprovement |



