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 PDCA Cycle |  Agile Example Mapping |  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. | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min pro Feature | 1 h bis mehrere Wochen | 30-60 min | 15-30 min |
Participantsdifferent | 3-6 | 1-8 | 3-7 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Example Map, Acceptance Criteria, Open Questions | Root cause notes, Countermeasures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Continuous improvementLeanExperiments | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeIncidentLeanProblem solving |