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 | ![]() UX Research Affinity Diagramming | ![]() Agile Three Amigos | ![]() 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 | 45–90 min | 15-30 min | 20-40 min pro Story |
Participantsdifferent | 3-7 | 3-10 | 3 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Theme clusters, Insight statements, Opportunity areas | Clarified Story, Test Examples, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | SynthesisQualitativeRoot cause | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsRefinementBehavior-Driven Development |



