View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Agile Acceptance Criteria Workshop | ![]() Agile Specification by Example |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 60-120 min | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 3-6 | 3-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






