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
Affinity Diagramming
UX Research
Affinity Diagramming
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
Empathy Mapping
UX Research
Empathy Mapping
Purposedifferent
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.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.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.
Complexitysame
LowLowLowLow
Timedifferent
45–90 min1-2 h15-45 min30–60 min
Participantsdifferent
3-103-101-34-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
Theme clusters, Insight statements, Opportunity areasArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
SynthesisQualitativeRoot cause
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
SynthesisQualitativeWorkshop
Add more methods