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 System Dynamics Simulation |  Delivery RAID Log |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. | 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. | 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 | High | Low | Low |
Timedifferent | Mehrere Tage bis Wochen | 30 min Setup, dann laufend | 15-45 min |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-3 maintaining, briefing for everyone | 1-3 |
Formatsame | Async | Async | Async |
Outputdifferent | Simulation Model, Scenario Reports | RAID Log, Status Report Source | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
