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 Specification by Example |  Facilitation Decision Jam |  Operations Kepner-Tregoe |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-90 min pro Feature | 60-90 min | 2-8 h | 15-30 min |
Participantsdifferent | 3-6 | 4-10 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Problem Cluster, Prioritized Challenge, Experiment | Problem Analysis, Decision Analysis, Risk Plan | Root cause notes, Countermeasures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | FacilitationDecisionProblem solvingWorkshop | Problem solvingRoot causeDecisionOperations | Root causeIncidentLeanProblem solving |