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 |  Decision Making Argument Mapping |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-120 min | 1-3 h | 1-4 h | 15-45 min |
Participantsdifferent | 2-8 | 1-8 | 1-5 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Argument Map, Evidence Gaps, Decision Rationale | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | SensemakingDecisionRationale | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |