View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Evaporating Cloud | ![]() Systems Thinking Leverage Points |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitydifferent | Low | High | Medium | High |
Timedifferent | 15-45 min | 2-4 h | 60-120 min | Half day |
Participantsdifferent | 1-3 | 3-8 | 2-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Leverage Map, Action Strategy |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingChangeStrategy |



