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 |  Innovation Contradiction Analysis |  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. | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | 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 | 60-120 min | 60-90 min pro Feature | 15-30 min |
Participantsdifferent | 3-7 | 2-8 | 3-6 | 2-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Example Table, Acceptance Tests | Root cause notes, Countermeasures |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ContradictionsInnovationProblem solving | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving |