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 A3 Problem Solving |  Agile Example Mapping |  Operations Gemba Walk |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 45-90 min | 30-60 min | 30-120 min |
Participantsdifferent | 3-6 | 2-5 | 3-7 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | A3 Report, Action Plan, Root Cause Analysis | Example Map, Acceptance Criteria, Open Questions | Observation Notes, Improvement Ideas |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | LeanProblem solvingCoachingOperations | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LeanObservationProcessOperations |