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 |  Delivery RAID Log |  Decision Making Red Teaming |  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. | 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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 | Low | High | Medium |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 1-4 h | 1-3 Tage |
Participantsdifferent | 1-3 | 1-3 maintaining, briefing for everyone | 3-8 | 1-4 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Challenge Findings, Risk Register, Mitigation Plan | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | RiskDecisionSensemaking | DocumentationStakeholdersArchitecture |