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 | ![]() Agile Specification by Example | ![]() Innovation Contradiction Analysis |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-60 min | 60-90 min pro Feature | 60-120 min |
Participantsdifferent | 3-7 | 3-6 | 2-8 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | ContradictionsInnovationProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






