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 |  Agile Example Mapping |  Operations After-Action Review |  Operations Learning 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Low | Low | Medium |
Timedifferent | 1-3 h | 30-60 min | 20-45 min | 1-3 h |
Participantsdifferent | 3-10 | 3-7 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Example Map, Acceptance Criteria, Open Questions | Lessons learned, Action items, Event summary | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | ProcessOperationsImprovement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LearningOperationsImprovement | LearningRetrospectiveIncidentOperations |