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 Architecture Decision Record |  Systems Thinking Intervention Mapping |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-120 min | 15-45 min | 1-5 Tage | 1-2 Tage |
Participantsdifferent | 2-8 | 1-3 | 4-12 | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | ADR File, Decision Log, Rationale | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureRationaleDocumentationGovernance | ChangeSystems thinkingCapability | ArchitectureDocumentationCommunication |