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 |  Agile Three Amigos |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 | Low | High |
Timedifferent | 60-120 min | 60-90 min pro Feature | 15-30 min | 2-4 h |
Participantsdifferent | 2-8 | 3-6 | 3 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Example Table, Acceptance Tests | Clarified Story, Test Examples, Open Questions | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | AgileRequirementsExamplesBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement | Theory of ConstraintsSystems thinkingChange |