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 Reverse Brainstorming | ![]() Innovation Design Charrette | ![]() 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. | 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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | 30-60 min | Halber Tag bis mehrere Tage | 20-40 min pro Story |
Participantsdifferent | 3-7 | 3-12 | 10-50 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Reverse Ideas, Risk Themes, Solution Ideas | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | BrainstormingIdeationCreativityRisk | BrainstormingWorkshopCollaborationIdeation | AgileRequirementsRefinementBehavior-Driven Development |



