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 Evaporating Cloud |  Architecture C4 Model |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | Medium | Low | High |
Timedifferent | 15-45 min | 60-120 min | 1-4 h | 2-4 h |
Participantsdifferent | 1-3 | 2-8 | 1-5 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Context Diagram, Container Diagram, Component Diagram | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureCommunicationVisualization | Theory of ConstraintsSystems thinkingChange |