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 A3 Problem Solving |  Operations Gemba Walk |  Agile Specification by Example |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 45-90 min | 30-120 min | 60-90 min pro Feature | 15-30 min |
Participantsdifferent | 2-5 | 2-6 | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Observation Notes, Improvement Ideas | Example Table, Acceptance Tests | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | LeanObservationProcessOperations | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving |