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 for Cynefin Workshop.
Decision Making
Cynefin Workshop
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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.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
LowHighMediumLow
Timedifferent
15-45 min1-4 h60-180 min1-2 Tage
Participantsdifferent
1-33-84-201-4
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleChallenge Findings, Risk Register, Mitigation PlanCynefin Map, Domain-specific Actions, Sensemaking NotesArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RiskDecisionSensemaking
ComplexitySensemakingDecision
ArchitectureDocumentationCommunication
Add more methods