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 Gemba Walk |  Operations Process 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 20-45 min | 30-120 min | 1-3 h |
Participantsdifferent | 3-6 | 3-12 | 2-6 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Lessons learned, Action items, Event summary | Observation Notes, Improvement Ideas | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | LearningOperationsImprovement | LeanObservationProcessOperations | ProcessOperationsImprovement |