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 After-Action Review |  Agile Example Mapping |  Operations A3 Problem Solving |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20-45 min | 30-60 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 3-7 | 2-5 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Example Map, Acceptance Criteria, Open Questions | A3 Report, Action Plan, Root Cause Analysis | Example Table, Acceptance Tests |
Tagsno overlap | LearningOperationsImprovement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LeanProblem solvingCoachingOperations | AgileRequirementsExamplesBehavior-Driven Development |