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 for Argument Mapping
Decision Making
Argument Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Affinity Diagramming
UX Research
Affinity Diagramming
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.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.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h1-2 h45–90 min15-45 min
Participantsdifferent
1-83-103-101-3
Formatdifferent
Workshop + asyncWorkshopWorkshopAsync
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesTheme clusters, Insight statements, Opportunity areasADR File, Decision Log, Rationale
Tagsno overlap
SensemakingDecisionRationale
CanvasArchitectureAlignmentWorkshop
SynthesisQualitativeRoot cause
ArchitectureRationaleDocumentationGovernance
Add more methods