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 showing three sorted card stacks and an open question about a possible group.
UX Research
Card Sorting
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations.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 problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitysame
LowLowLowLow
Timedifferent
20-45 min15-45 min30-60 min1-2 Tage
Participantsdifferent
Based on research question1-32-81-4
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Content groups, Label set, IA hypothesesADR File, Decision Log, RationaleFishbone Diagram, Cause Categories, Investigation BacklogArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Information architectureNavigationStructure
ArchitectureRationaleDocumentationGovernance
Root causeQualityOperations
ArchitectureDocumentationCommunication
Add more methods