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 |  Systems Thinking Evaporating Cloud |  Systems Thinking Leverage Points |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 60-90 min pro Feature | 60-120 min | Half day | 2-4 h |
Participantsdifferent | 3-6 | 2-8 | 3-12 | 3-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Leverage Map, Action Strategy | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingChangeStrategy | Theory of ConstraintsSystems thinkingChange |