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 |  Operations 8D Problem Solving |  Agile Specification by Example |
|---|---|---|---|---|
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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 30-60 min | 45–90 min | 1-6 Wochen | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 3-10 | 4-10 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Theme clusters, Insight statements, Opportunity areas | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | SynthesisQualitativeRoot cause | QualityProblem solvingRoot cause | AgileRequirementsExamplesBehavior-Driven Development |