View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Contradiction Analysis |  Agile Example Mapping |  Agile Acceptance Criteria Workshop |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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-120 min | 30-60 min | 20-40 min pro Story | 15-30 min |
Participantsdifferent | 2-8 | 3-7 | 3-6 | 2-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update | Root cause notes, Countermeasures |
Tagsno overlap | ContradictionsInnovationProblem solving | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development | Root causeIncidentLeanProblem solving |