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 Scatter Diagram with its method-specific working model.
Operations
Scatter Diagram
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage45–90 min30-90 min15-45 min
Participantsdifferent
1-43-101-41-3
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewTheme clusters, Insight statements, Opportunity areasScatter Plot, Korrelationsnotiz, HypothesenlisteADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
SynthesisQualitativeRoot cause
Root causeQualityVisualization
ArchitectureRationaleDocumentationGovernance
Add more methods