View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 5 Whys |  Agile Example Mapping |  UX Research Affinity Diagramming |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 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 | 15-30 min | 30-60 min | 45–90 min | 20-40 min pro Story |
Participantsdifferent | 2-6 | 3-7 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Root cause notes, Countermeasures | Example Map, Acceptance Criteria, Open Questions | Theme clusters, Insight statements, Opportunity areas | Acceptance Criteria, Story Update |
Tagsno overlap | Root causeIncidentLeanProblem solving | Behavior-Driven DevelopmentRequirementsExamplesRefinement | SynthesisQualitativeRoot cause | AgileRequirementsRefinementBehavior-Driven Development |