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 Gemba Walk |  Agile Specification by Example |  Operations Process Mapping |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-120 min | 60-90 min pro Feature | 1-3 h | 30-60 min |
Participantsdifferent | 2-6 | 3-6 | 3-10 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Observation Notes, Improvement Ideas | Example Table, Acceptance Tests | Process Map, Handoff List, Improvement Backlog | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | LeanObservationProcessOperations | AgileRequirementsExamplesBehavior-Driven Development | ProcessOperationsImprovement | Behavior-Driven DevelopmentRequirementsExamplesRefinement |