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 ABC Analysis |  Operations A3 Problem Solving |  Operations 5 Whys |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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 | 60-90 min pro Feature | 30-60 min | 45-90 min | 15-30 min |
Participantsdifferent | 3-6 | 1-5 | 2-5 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | ABC Classification, Focus Rules, Control List | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | PrioritizationOperationsPortfolio | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving |