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 Decision Jam |  Operations Kepner-Tregoe |  Agile Specification by Example |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | High | Medium | Low |
Timedifferent | 60-90 min | 2-8 h | 60-90 min pro Feature | 15-30 min |
Participantsdifferent | 4-10 | 2-8 | 3-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Problem Cluster, Prioritized Challenge, Experiment | Problem Analysis, Decision Analysis, Risk Plan | Example Table, Acceptance Tests | Root cause notes, Countermeasures |
Tagsno overlap | FacilitationDecisionProblem solvingWorkshop | Problem solvingRoot causeDecisionOperations | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving |