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 |  Decision Making Red Teaming |  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. | 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. | 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 | 1-4 h | 30 min Setup, dann laufend | 1-3 Tage |
Participantsdifferent | 1-3 | 3-8 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Challenge Findings, Risk Register, Mitigation Plan | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskDecisionSensemaking | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture |