View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Fishbowl Discussion | ![]() Agile Example Mapping | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | When a controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 8-80 | 3-7 | 3-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Discussion Insights, Observed Tensions, Follow-up Questions | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | FacilitationDialogueLarge group | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






