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 Gemba Walk |  Operations 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-120 min | 15-30 min | 45-90 min |
Participantsdifferent | 3-6 | 2-6 | 2-6 | 2-5 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Observation Notes, Improvement Ideas | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | LeanObservationProcessOperations | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |