methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.
Complexitydifferent
LowHighLowLow
Timedifferent
15-45 min1-4 h30-60 min1-2 Tage
Participantsdifferent
1-33-83-101-4
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleChallenge Findings, Risk Register, Mitigation PlanRisk Matrix, Top Risk ListArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RiskDecisionSensemaking
RiskDecisionPrioritizationAssessment
ArchitectureDocumentationCommunication
Add more methods