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 |  Architecture arc42 |  Decision Making Argument Mapping |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 15-45 min | 1-4 h | 1-2 Tage | 1-3 h |
Participantsdifferent | 1-3 | 3-8 | 1-4 | 1-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Challenge Findings, Risk Register, Mitigation Plan | Architecture Document, Context View, Runtime View, Deployment View | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskDecisionSensemaking | ArchitectureDocumentationCommunication | SensemakingDecisionRationale |