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 | ![]() Innovation Morphological Analysis | ![]() Agile Specification by Example |
|---|---|---|---|---|
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. | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 60-120 min | 1-3 h | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-8 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Morphological Box, Concept Combinations, Idea Shortlist | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ContradictionsInnovationProblem solving | IdeationInnovationCreativity | AgileRequirementsExamplesBehavior-Driven Development |



