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 Soft Systems Methodology | ![]() Delivery RAID Log | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 15-45 min | 0.5-3 Tage | 30 min Setup, dann laufend | 1-3 Tage |
Participantsdifferent | 1-3 | 5-15 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Soft systemsComplexitySensemakingSystems thinking | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture |



