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 Brainstorming |  Innovation Reverse Brainstorming |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 30-60 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 3-7 | 4-12 | 3-12 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Idea pool, Theme clusters, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityRisk | AgileRequirementsRefinementBehavior-Driven Development |