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 5 Whys |  Agile Specification by Example |  Operations 8D Problem Solving |
|---|---|---|---|---|
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 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. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30-60 min | 15-30 min | 60-90 min pro Feature | 1-6 Wochen |
Participantsdifferent | 3-7 | 2-6 | 3-6 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Root cause notes, Countermeasures | Example Table, Acceptance Tests | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeIncidentLeanProblem solving | AgileRequirementsExamplesBehavior-Driven Development | QualityProblem solvingRoot cause |