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 Acceptance Criteria Workshop | ![]() Innovation Contradiction Analysis | ![]() Innovation TRIZ |
|---|---|---|---|---|
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 story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30-60 min | 20-40 min pro Story | 60-120 min | 1-4 h |
Participantsdifferent | 3-7 | 3-6 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Contradiction Statement, Inventive Principles, Solution Concepts |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development | ContradictionsInnovationProblem solving | InnovationProblem solvingContradictionsCreativity |



