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 | ![]() Architecture Request for Comments | ![]() 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 |
Timedifferent | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h |
Participantsdifferent | 2-8 | 3-20 Reviewer | 3-8 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureDecisionAsyncGovernance | Theory of ConstraintsSystems thinkingChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






