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 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
Paper illustration for ABC Analysis
Operations
ABC Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.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
15-45 min30-60 min30-60 min1-2 Tage
Participantsdifferent
1-32-81-51-4
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleFishbone Diagram, Cause Categories, Investigation BacklogABC Classification, Focus Rules, Control ListArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
Root causeQualityOperations
PrioritizationOperationsPortfolio
ArchitectureDocumentationCommunication
Add more methods