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 Example Mapping |  Operations A3 Problem Solving |  Agile Specification by Example |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 45-90 min | 60-90 min pro Feature | 15-30 min |
Participantsdifferent | 3-7 | 2-5 | 3-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | A3 Report, Action Plan, Root Cause Analysis | Example Table, Acceptance Tests | Root cause notes, Countermeasures |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LeanProblem solvingCoachingOperations | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving |