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 Specification by Example | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Leverage Points |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 60-120 min | 60-90 min pro Feature | 2-4 h | Half day |
Participantsdifferent | 2-8 | 3-6 | 3-8 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Example Table, Acceptance Tests | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Leverage Map, Action Strategy |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | AgileRequirementsExamplesBehavior-Driven Development | Theory of ConstraintsSystems thinkingChange | Systems thinkingChangeStrategy |



