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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
HighLowLowLow
Timedifferent
1-4 h1-2 h15-45 min30-60 min
Participantsdifferent
3-83-101-32-10
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
RiskDecisionSensemaking
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernanceAlignment
Add more methods