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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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
Empathy Mapping
UX Research
Empathy Mapping
Purposedifferent
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 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.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
1-2 Tage45–90 min15-45 min30–60 min
Participantsdifferent
1-43-101-34-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewTheme clusters, Insight statements, Opportunity areasADR File, Decision Log, RationaleEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
ArchitectureDocumentationCommunication
SynthesisQualitativeRoot cause
ArchitectureRationaleDocumentationGovernance
SynthesisQualitativeWorkshop
Add more methods