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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration for Argument Mapping
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.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 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.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
LowLowMediumMedium
Timedifferent
15-45 min1-2 Tage60-180 min1-3 h
Participantsdifferent
1-31-44-201-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment ViewCynefin Map, Domain-specific Actions, Sensemaking NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
ComplexitySensemakingDecision
SensemakingDecisionRationale
Add more methods