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 |  Delivery RAID Log |  Architecture Views and Beyond |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | Medium | Low |
Timedifferent | 60-120 min | 30 min Setup, dann laufend | 1-3 Tage | 15-45 min |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 1-4 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |