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 | ![]() Agile Example Mapping | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|
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 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 60-120 min |
Participantsdifferent | 3-6 | 3-7 | 2-8 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






