View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Operations After-Action Review |  Operations A3 Problem Solving |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | 20-45 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-6 | 3-12 | 2-5 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Lessons learned, Action items, Event summary | A3 Report, Action Plan, Root Cause Analysis | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | LearningOperationsImprovement | LeanProblem solvingCoachingOperations | Behavior-Driven DevelopmentRequirementsExamplesRefinement |